Loading...
Loading...
Found 10,524 Skills
Use this when the user requests you to execute multiple tasks in parallel, start multiple workers/agents simultaneously, launch multiple independent sessions using tmux, prevent PM from directly bypassing implementation protocols, or when you act as a PM to decompose and assign tasks to multiple independent workers. Trigger terms include "parallel execution", "start multiple", "simultaneous execution", "assign workers", "multi-agent parallelism", "start workers", "tmux launch", "independent session", "anti-escape", "task assignment", "do together". Do not use for single short tasks, cross-platform task status management, or Git branch/commit/PR/merge security rules.
Session mode: act as orchestrator brain only. Research and implementation go to cheaper-model subagents; the orchestrator scopes, briefs, verifies, and judges. User-invoked with the task as the argument.
fix a Linear ticket end to end, fetch it, branch, plan with confirmation, implement, review. Triggers: fix a Linear ticket, work on a Linear issue, implement a Linear ticket, resolve a Linear bug. Flags: --base <branch> (default main) and an explicit ticket ID.
notify the user via Discord webhook embed. Triggers: /notify, send a Discord notification, alert me when done, ping me on Discord. Flags: --task, --link, --webhook, --color, --field, --content, --dry-run.
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
handoff the session, compact the conversation into a document a fresh agent can resume from, or restore context from a saved handoff. Triggers: /handoff, save session context, hand off to a new agent, resume from a handoff file. Flags: --resume <path>, --path <path>, and a positional focus argument.
make a pull request with a plain-English title and a thematic summary built from the branch diff. Triggers: open a PR, create a pull request, submit a PR. Flags: --target <branch> (default main), --ticket <id> (prefix title with the ticket), --conventional (conventional-commit title).
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.