add-dictation — Use when the user runs /add-dictation or wants speech turned into text with Grok speech-to-text: a mic button that dictates into the composer, live captions.
add-read-aloud — Use when the user runs /add-read-aloud or wants the app to speak text with Grok text-to-speech: read-aloud button on assistant replies, auto-speak, TTS.
add-voice — Use when the user runs /add-voice, types Voice Mode, or asks to add Grok realtime voice to an app.
advisor — Advisor mode. Consult a stronger (or different) model at key checkpoints: before major decisions, when stuck on an error, and before declaring a task done.
architect — Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
arena — Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.
automate-me — Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill".
blast-radius — Find what a change could break somewhere else before it ships, beyond the diff.
bro — Restate the last message in plain human language, with no jargon.
cancel-ralph — Cancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.
cli-for-agents — Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors.
continual-learning — Orchestrate continual learning by delegating transcript mining and AGENTS.md updates to `agents-memory-updater`.
control-cli — Build or adapt a local harness to drive, inspect, and profile an interactive CLI or TUI without external services.
control-ui — Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI.
create-learning-path — Build a personalized learning roadmap with milestones and practice checkpoints
create-plugin-scaffold — Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring.
create-verification-skill — Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
cursor-sdk — Guide users building apps, scripts, CI pipelines, or automations on top of the Cursor TypeScript SDK (`@cursor/sdk`).
debug-voice — Use when the user runs /debug-voice, says voice mode has flaws, asks to see or capture what happened in a Grok realtime voice session.
deslop — Remove AI-generated code slop and clean up code style
docs-canvas — Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections.
figure-it-out — 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.
fix-ci — Find failing PR checks, inspect logs or external check links, and apply focused fixes
fix-merge-conflicts — Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution
get-pr-comments — Fetch and summarize review comments from the active pull request
google-docs — Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers/footers.
google-sheets — Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation.
google-slides — Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling.
how — Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live".
interrogate — Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart".
loop-on-ci — Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
maintain-verification-skill — Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature.
Make Bot UI — Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key.
make-pr-easy-to-review — Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.
new-branch-and-pr — Create a fresh branch, complete work, and open a pull request
no-comments — Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
orchestrate — Use only when the user explicitly types `/orchestrate <goal>` to decompose a large task.
Poteto Mode — poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work.
pr-review-canvas — Generate an interactive PR review walkthrough as an HTML page.
principle-foundational-thinking — Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share.
principle-laziness-protocol — Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading.
principle-make-operations-idempotent — Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries.
principle-model-the-domain — Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
principle-never-block-on-the-human — Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact.
principle-sequence-verifiable-units — Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs.
principle-subtract-before-you-add — Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
principle-test-behavior-not-implementation — Apply when you write, change, or keep a test. Call the code the way its users do and assert the result they observe against a literal expected value.
principle-type-system-discipline — Apply when designing types, reviewing a function signature, or writing code in any statically-typed language.
ralph-loop — Start a Ralph Loop for iterative self-referential development.
ralph-loop-help — Explain the Ralph Loop plugin, how it works, and available skills.
recall — Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents).
reflect — Spawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill.
reproduce-and-fix-issues — Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes.
review-and-ship — Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
review-plugin-submission — Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.
run-learning-retrospective — Evaluate learning progress, identify blockers, and adjust the learning plan
run-smoke-tests — Run Playwright smoke tests, debug failures, and verify fixes
setup-benny — Configure Benny and prepare its triage and repro automations.
setup-pstack — Configure which models pstack uses per role and at what reasoning budget.
show-me-your-work — Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).
swarm — Fan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.
tdd — 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.
teach — Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation.
technical-writing — Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax.
thermo-nuclear-code-quality-review — Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth.
thermo-nuclear-review — Comprehensive security and correctness audit of a branch's changes.
thermos — Launch both thermo-nuclear review subagents in parallel, then synthesize their findings.
triage-issue-reports — Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation.
typescript-best-practices — TypeScript best practices. Use when reading or editing any .ts or .tsx file.
unslop — Cut AI tells from any writing. Must always apply.
verify-this — Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED.
weekly-review — Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work
what-did-i-get-done — Summarize authored commits over a user-specified time period into a concise update
why — Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds.
workflow-from-chats — Extract durable working preferences from recent Cursor chats and convert them into skills, rules, or workflow docs.
X Chat — Read, summarize, or send encrypted X Chat (XChat) DMs via the X plugin MCP plus local chatxdk / xchat_lite.py. Use when the user mentions X Chat, xchat.
X MCP guide — ALWAYS read this when a user connects the X plugin or any X MCP, before using any X connection, and again on any X error.
X Money guide — Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability.