Loading...
Loading...
Found 12 Skills
Design a SaaS product's MCP server as a product surface AI agents operate - sizing the build investment, curating a 5-15 workflow-tool agent surface instead of mirroring API endpoints, named write-tool safety patterns (scoped credentials, read-only lockdown, human-in-the-loop approval, risk-tiered server-side gates, dry-run preflight, idempotency and spend caps), remote hosting with OAuth 2.1, versioning the tool surface, MCP registry discoverability, and measuring agent adoption. Use whenever the user mentions MCP, Model Context Protocol, an agent-facing tool surface, exposing a product to AI agents or coding assistants, or MCP write-tool safety - even if they never say "MCP server". Design layer only - code-generation MCP builder skills scaffold what this specifies.
Fetch ALL unresolved PR conversations — review threads, review body comments, and regular PR comments — then output a strict /tdd plan with atomic commits that fixes and replies to every one. Use this skill whenever the user wants to resolve, address, or fix PR review feedback, comments, threads, nitpicks, or suggestions from any reviewer (human or bot like CodeRabbit, Copilot, etc.). Triggers on phrases like "resolve PR threads", "fix PR comments", "address review feedback", "resolve conversations".
Author a new OM skill from a brief, or split an oversized SKILL.md into layered references/ files — conservatively, behind the lint + completeness gate. Knows the layering philosophy, lint invariants, tracker abstraction, and the cross-skill contract, so output matches house conventions. Use for "create a skill for…", "new om-skill", "split this skill into references".
Generate a GROOVE.md onboarding guide for contributors to a groove-enabled project. Explains the compound loop, commands, and conventions.
Analyse task status and distribution across the configured backend.
Execute a trivial task inline — no subagents, no planning overhead
Capture explored work as a backlog item for future implementation. Use when you've explored an enhancement, alternative approach, or feature but decided to defer it. Creates comprehensive plan files in backlog/ directory with enough context for a future session to execute efficiently.
Diagnose Zapier Workflows skill and SDK CLI compatibility. Use when a workflow skill asks for a compatibility check, when SDK commands or flags are missing, when a workflow skill may be stale, or when updating workflow skills after an SDK CLI change.
Thin router for Pipefy build and configure asks: map user intent to the correct domain skill (pipes, automations, AI agents, iPaaS, portals, etc.). Use when the user wants to create, build, configure, or integrate something in Pipefy and you need to know which skill to open. Do not use this skill as a delivery playbook — if the user already has a building skill or a detailed build prompt, follow that for how to build; use this skill only for which Pipefy domain skill to read.
Use this skill when you need a standardized Claude Code workflow toolkit. It covers claudekit plugin installation, init-wizard scaffolding for rules/modes/hooks/MCP, and safe operating guidance for team adoption.
Organize research, constructs, design, samples, results, biases, conflicts, and gaps into a traceable evidence map. Use when the user asks for "create an evidence map", "organize research conflicts", "connect literature", or requests the rw-evidence-map workflow. Runs without a private local workspace or preset research-lab; use user-provided material and bundled public-source methods.
[DEPRECATED] Use /ce:compound instead — renamed for clarity.