Loading...
Loading...
Found 335 Skills
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines. Subagent routing is handled automatically via PreToolUse hook.
Use when validating implementation against spec artifacts before archive — not for design, planning, or implementation
Orchestrate level design team: level-designer + narrative-director + world-builder + art-director + systems-designer + qa-tester for complete area/level creation.
Document and communicate plans clearly. Structures implementation plans with tasks, decisions, and success criteria.
Use when extracting imperatives from agent instruction files, analyzing rule coverage, or preparing input for /policy-algebra and /distill.
Analyzes high-performing content from URLs and builds a swipe file
[Utilities] ⚡⚡⚡⚡⚡ Bootstrap a new project step by step
Analyze OpenCode conversation history to identify themes and patterns in user messages. Use when asked to analyze conversations, find themes, review how a user steers agents, or extract insights from session history.
Drive development using delegated agent workflows. Coordinates multi-agent task execution with proper supervision and result integration.
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Request peer review with proper context and preparation. Structures review requests with clear description of changes and testing status.
Capture noteworthy review violations for the eval framework. Use when validator-run finds review failures — judges violations and saves notable ones to evals/inventory.yml.