Loading...
Loading...
Found 149 Skills
Evaluate and improve skills through measured testing. Run trigger evaluations to test whether skill descriptions cause correct activation, optimize descriptions via automated train/test loops, benchmark skill output quality with A/B comparisons, and validate skill structure. Use when user says "improve skill", "test skill triggers", "optimize description", "benchmark skill", "eval skill", or "skill quality". Do NOT use for creating new skills (use skill-creator-engineer).
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".
FFmpeg-based 4-step video creation: Validate, Prepare, Encode, Verify. Use when user wants to combine a static image with audio to create an MP4 video, create a music video from cover art, or produce podcast/YouTube video from an image and audio file. Use for "image to video", "static video", "mp4 from image", "album art video", or "audio visualization". Do NOT use for video editing, live streaming, or generating images.
Perses-aware code review: check Go backend against Perses patterns, React components against Perses UI conventions, CUE schemas against plugin spec, and dashboard definitions against best practices. Dispatches appropriate sub-reviewers. Use for "review perses", "perses pr", "perses code review". Do NOT use for general Go/React review without Perses context.
Constructive critique through 5 HackerNews commenter personas with evidence-based claim validation. Use when user wants devil's advocacy, stress testing, or critical review of ideas, docs, architecture, or code. Use for "roast", "critique this", "poke holes", "devil's advocate", "stress test", or "what's wrong with". Do NOT use for code review (use systematic-code-review), implementation changes, or performance profiling without a specific critique request.
Transform dense technical communication into clear, structured business formats using proposition extraction and deterministic templates. Use when user needs to convert technical updates, debugging narratives, status reports, or dependency discussions into executive-ready summaries. Use for "transform this update", "make this executive-ready", "summarize for my manager", "professional format", or "status report". Do NOT use for writing new content from scratch, creative writing, or generating documentation that doesn't transform an existing input.
CI/CD pipeline patterns for GitHub Actions, GitLab CI, testing strategies, and deployment automation
Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
Kubernetes operations including manifests, Helm charts, operators, troubleshooting, and resource management
Advanced git workflows including worktrees, bisect, interactive rebase, hooks, and recovery techniques
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.
Run quality gates on implemented feature: tests, lint, type checks, and custom validation. Use after /feature-implement completes. Use for "validate feature", "run quality gates", "check feature", or "/feature-validate". Do NOT use for ad-hoc linting or debugging.