Loading...
Loading...
Found 7,458 Skills
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.
Use when orchestrating multi-agent teams for parallel work — feature dev, quality audits, research sprints, bug hunts, or any task needing 2+ agents working concurrently
Use when setting up a new AI agent from scratch — asks 10 discovery questions, configures the correct files for the target system, tests integrations, and implements security guardrails
Classify user requests and route to the correct agent + skill combination. Use for any user request that needs delegation: code changes, debugging, reviews, content creation, research, or multi-step workflows. Invoked as the primary entry point via "/do [request]". Do NOT handle code changes directly - always route to a domain agent. Do NOT skip routing for anything beyond pure fact lookups or single read commands.
Interactive guide to repository workflow system: agents, skills, routing, and execution patterns. Use when user asks how the system works, what commands are available, or how to use brainstorm/plan/execute phases. Use for "how does this work", "what can you do", "explain workflow", "help me understand", or "show me the process". Do NOT use for actually executing workflows (use workflow-orchestrator) or debugging (use systematic-debugging).
Zero-ceremony inline execution for tasks completable in 3 or fewer file edits. No plan, no subagent, no research — just understand, do, commit, log. Use for "quick fix", "typo fix", "one-line change", "trivial fix", "rename this variable", "update this value", "fix this import". Do NOT use for tasks requiring research, planning, new dependencies, or more than 3 file edits — redirect to /quick instead.
Interact with the learning system: show stats, list/search accumulated knowledge, and graduate mature entries into agents/skills. Backed by learning.db (SQLite + FTS5). Use when user says "retro", "retro list", "retro search", "retro graduate", "check knowledge", "what have we learned", "knowledge health", "graduate knowledge".
Break a design document into wave-ordered implementation tasks with domain agent assignments. Use after /feature-design produces a design doc. Use for "plan feature", "break down design", "create tasks", or "/feature-plan". Do NOT use without a design doc or for simple single-task work.
Collaborative coding with enforced micro-steps: announce, show diff, wait for confirmation, apply, verify. User controls pace with commands. Works with any domain agent as the executor. Use when: "pair program", "pair with me", "let's code together", "step by step coding", "walk me through implementing", "code with me"
Maintain /do routing tables and command references when skills or agents are added, modified, or removed. Use when skill/agent metadata changes, after skill-creator-engineer or agent-creator-engineer runs, or when routing tables need synchronization. Use for "update routes", "sync routing", "routing table", or "refresh /do". Do NOT use for creating new skills/agents, modifying skill logic, or manual /do table edits.
Gold-standard code review for SAP CC Go repositories against the project's lead review standards. Dispatches 10 domain-specialist agents in parallel — each loads domain-specific references and scans ALL packages for violations in their assigned domain. Produces a prioritized report with REJECTED/CORRECT code examples. Optional --fix mode applies corrections on a worktree branch. This is the definitive "would this code pass lead review?" assessment.
Spawn 10 independent parallel agents to analyze source material from distinct perspectives, synthesize findings, and apply improvements to a target agent or skill. Use when source material is complex and multi-angle extraction justifies 3-5x token cost over inline analysis. Use for "parallel analysis", "multi-perspective", or "deep extraction". Do NOT use for routine improvements, simple source material, or when token budget is limited.