Productivity

fightzy Bundle

Review durable guidance at task closure, or when explicitly asked to optimize reusable context using existing work evidence; propose changes to content, scope, or loading.

fightzy Bundle

Use when a user wants to evaluate a product, startup, feature, or workflow idea by clarifying the idea through dialogue, researching similar products and discussions, comparing alternatives, assessing market crowdedness, deep-diving leading competitors and persistent user complaints in crowded spaces, and deciding whether to continue, pivot, or stop.

fightzy Skill

Use when a non-trivial change should follow an OpenSpec-plus-superpower workflow with formal specs, approval gates, implementation discipline, and no parallel planning system

intelligent-internet Bundle

Use this skill for everyday work with the user's connected accounts through Genii integrations: Gmail and Google Calendar. Trigger it when the user asks to read or send email, check or schedule calendar events, connect one of these accounts, or create an ongoing Gmail or Calendar watch. It drives the backend-proxied `composio_*` tools from the genii-integrations plugin.

ivan-gerasimov-1 Bundle

Create TASK records by splitting a CHANGE into reviewable implementation checkpoints

jackchuka Bundle

End-to-end work session on a GitHub Project item. Setup → Clarify → Plan → Implement → PR, with decisions captured throughout. Use when starting work on an issue, picking up a task, or resuming an interrupted session.

jasonku09 Bundle

Execute the next task of a free local or server-planned Altitude learning project — small code steps with fill-in placeholders, predict-before-run checks, and evidence-based review. Use when the user says "next lesson", "let's continue the project", "next task", or invokes /next-lesson.

jcosta33 Skill

Split a ready Suspec spec into collision-proof task packets. Use when spec-governed work must be divided into independent parallel slices, repository or platform contexts, or dispatchable transformation waves. Do not use for unspecced work or work with no dispatch boundary.

jessedegans Skill

Use before starting any feature, entering unfamiliar code, or beginning a non-trivial task. Enforces understanding before action. No code, no scaffolding, no implementation until the problem is explored and a direction is approved. Use when: user says "let's build X", "add feature Y", "I want to create Z", or begins work on something that needs design thinking.

jojoprison Bundle

Use proactively mid-task, on your own initiative, whenever past work might already cover the current step — before re-fixing a recurring or previously-seen bug, touching an unfamiliar subsystem, or making a risky/hard-to-reverse change — not only when asked. Also when the user wants to recall prior context: 'what did we decide about X', 'find everything about Y', 'что мы решили про', 'что мы знаем', 'как мы делали', 'когда последний раз', 'такое уже было', 'вспомни', 'напомни', 'посмотри в памяти', 'найди в памяти', 'как решали', 'где ещё может быть', 'что было с', or similar. Synthesizes across notes with source citations; prefer over generic memory tools when an Obsidian vault is available.

mergifyio Skill

Use Mergify config commands to validate configuration files, simulate Mergify actions, and write Mergify configuration. ALWAYS use this skill when validating, writing, editing, or simulating Mergify config. Triggers on config validate, config simulate, mergify configuration, mergify.yml, .mergify.yml, merge queue config, workflow rules, conditions.

moshthepitt Bundle

Host-side Email work-inbox channel for LionClaw.

moshthepitt Bundle

Handle LionClaw email-channel turns and replies without touching mailbox credentials or raw mail transport.

mozilla-platform-ops Bundle

Diagnose why a Taskcluster worker pool queue is backed up. Checks pool health (pending tasks, capacity, provisioning errors) via Taskcluster CLI and analyzes demand patterns (queue times, task volume by project, top pushers) via BigQuery. Produces a diagnostic summary identifying demand-side vs supply-side causes. Use whenever a worker pool has high pending counts, elevated queue times, or deadline-exceeded expirations. Also use when someone asks "why is the queue backed up", "why are tasks waiting", "what's wrong with <pool>", or mentions pending task counts for any gecko-t or releng-hardware pool.

mpagot Skill

Creates a GitHub pull request from staged git changes, handling commit, push, and PR creation in one workflow. Activate when the user asks to "create PR", "open pull request", "push and create PR", "submit PR", or wants to send their changes upstream to os-autoinst-distri-opensuse.

msutara Skill

Cross-repo release workflow for all Config Manager repositories. Validates every repo (clean tree, build, test, lint), determines release scope, tags in multi-wave dependency order with per-repo independent version timelines and go.mod sync between waves, generates rich release notes with repo context and categorized changelogs, creates GitHub releases, verifies CI artifacts, and updates the project board. Each repo maintains its own version — a bump type (patch/minor/major) is applied to each repo's last tag independently. The reference repo (core) is always included as the product umbrella. Includes rollback/recovery for partial releases. USE FOR: release, tag repos, create release, bump version, release all repos, retag, cm release, new release, publish release, tag all, version bump.

msutara Skill

Full PR lifecycle management for the Config Manager project. Orchestrates the entire flow from local validation through fleet review, commit, push, PR creation, project board updates, CI monitoring, comment triage, and merge. Enforces the strict cm development workflow across all CM Go repos with mandatory safety gates at every irreversible step. USE FOR: create pr, submit pr, pr workflow, push and pr, cm pr, full pr cycle, run pr workflow, pr lifecycle, submit changes.

mudrii Skill

Use when creating, modifying, or debugging YAML workflow definitions or the workflow engine

mudrii Bundle

Use before making meaningful code changes in HOM to load repository architecture, workflow rules, crate boundaries, feature flags, and verification requirements

ob-labs Bundle

Use when helping with AgentSeek-managed projects or AgentSeek-compatible templates: create projects, diagnose lifecycle issues, run doctor/dev/info/task commands, edit lifecycle specs, or maintain Cookiecutter template inputs. Prefer public AgentSeek CLI and template contracts.

opascope Bundle

Surface the guesses in a task before starting. Use when asked to interrogate, grill, ask questions first, or clarify an underspecified request. Produces a short execution brief and only asks questions that would change the work.

opascope Bundle

Preserve verified progress so a new session can resume with no memory of this one. Use when asked to write a handoff, log progress, leave pickup notes, or resume a previous task. Records completed work, the exact next action, decisions, blockers and the files to read first.

openvinotoolkit Skill

Open a pull request to openvinotoolkit/openvino.genai. Use when: submitting changes, creating PR, opening pull request, pushing work for review, finalizing a task with a PR.

osovv Bundle

Use when the user explicitly selects the native spec-package workflow — interview the user, propose approaches, present a design, and write spec.xml plus an optional design-context.xml under .vvoc/specs/YYYY-MM-DD-<slug>/

osovv Skill

Use for review requests — routes to reviewer sub-agents through a vvoc review-only workflow, reports findings, and stops before fixes

osovv Skill

Use when the user explicitly selects the native plan-package execution workflow — validate an approved plan.xml, choose an execution mode with the user, and execute tasks with verification and commits

pchalupa Bundle

Create and maintain a RAID log, the register of a project's risks, assumptions, issues, and dependencies. Use when the user wants to start or update a RAID log, record a risk, blocker, assumption or dependency, prepare the log for a status meeting, or invokes a `/raid` command. For a settled technical decision use an ADR; for an open one an RFC.

pedromneto97 Bundle

**WORKFLOW SKILL** — Short guidance for the data layer in Flutter Clean Architecture (dio + json_serializable).

pedromneto97 Bundle

**WORKFLOW SKILL** — Minimal guidance for the domain layer in Flutter Clean Architecture (use `equatable`, `call()` pattern).

pedromneto97 Skill

**WORKFLOW SKILL** — Opinionated conventions for the presentation layer in Flutter Clean Architecture (pages, cubits, widgets, localization).

pluginagentmarketplace Bundle

Guide TDD workflow, design tests, and create mocking strategies

posit-dev Bundle

Generate synthetic datasets with Pointblank using Schema and field classes. Covers IntField, FloatField, StringField, BoolField, DateField, DatetimeField, and more. Supports presets (name, email, address, etc.), country-specific data, nullable columns, unique constraints, and profile_fields() for person data. Use when creating test data, fixtures, or synthetic datasets for validation testing.

posit-dev Bundle

Write data-validation plans with Pointblank. Covers choosing the right validation methods for each data quality concern, composing multi-step plans, setting thresholds and actions, using segments, conditional steps, handling nulls and missing values, and extracting results. Use when building or improving a validation workflow.

jonisavo Bundle

Use ONLY when the user explicitly requests the full end-to-end Supersigil workflow — from feature idea through verified specs to implementation. This is the guided "omakase" flow. For just writing specs, use ss-feature-specification. For just implementing, use ss-feature-development.

josemvcerqueira Bundle

Route a Sui Move task to the smallest applicable skill sequence. Requires the complete suite installation to execute a route.

jovandyaz Skill

Manages this repository's GitHub-native stacked PR workflow with the gh-stack extension, CodeRabbit review, and branch conventions. Use when creating PRs, splitting work into a stack, linking existing PRs, merging a stack, or responding to CodeRabbit. Commit messages still follow the repository's Conventional Commit policy.