Loading...
Loading...
Found 141 Skills
Decision-first data analysis with statistical rigor gates. Use when analyzing CSV, JSON, database exports, API responses, logs, or any structured data to support a business decision. Handles: trend analysis, cohort comparison, A/B test evaluation, distribution profiling, anomaly detection. Do NOT use for codebase analysis (use codebase-analyzer), codebase exploration (use explore-pipeline), or ML model training.
Full-repo SAP Converged Cloud Go compliance audit. Reviews every package against established review standards — focusing on over-engineering, error message quality, dead code, interface contracts, copy-paste structs, and pattern consistency with keppel. Dispatches parallel agents by package group, each reading ALL sapcc rules. Produces code-level findings with actual before/after diffs. Invoked via "/sapcc-audit" or through /do.
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.
Go error handling patterns: wrapping with context, sentinel errors, custom error types, errors.Is/As chains, and HTTP error mapping. Use when implementing error returns, defining package-level errors, creating custom error types, wrapping errors with fmt.Errorf, or checking errors with errors.Is/As. Use for "error handling", "fmt.Errorf", "errors.Is", "errors.As", "sentinel error", "custom error", or "%w". Do NOT use for general Go development, debugging runtime panics, or logging strategy.
Manually teach Claude Code an error pattern and its solution, storing it in the learning database with high confidence. Use when user provides an explicit "error -> solution" pair, wants to pre-load fix knowledge, or corrects a previous bad fix. Use for "/learn", "teach pattern", "remember this fix". Do NOT use for automatic error learning (that is the error-learner hook), debugging live issues, or querying existing patterns.
Resolve implementation ambiguities before planning begins. Two modes: Discussion mode surfaces gray areas with concrete options for greenfield work. Assumptions mode reads the codebase, forms evidence-based opinions, and asks the user to correct only what's wrong (brownfield work). Use for "discuss ambiguities", "resolve gray areas", "clarify before planning", "assumptions mode", "what are the gray areas", "before we plan". Do NOT use for broad design exploration (use feature-design) or for planning itself (use feature-plan).
Condition-based polling and retry patterns: exponential backoff, health checks, rate limit recovery, circuit breakers. Use when replacing arbitrary sleeps with condition checks, implementing retry logic, waiting for service availability, or handling API rate limits. Use for "wait for", "poll until", "retry with backoff", "health check", or "rate limit". Do NOT use for async event-driven architectures, distributed locking, or real-time guarantees.
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.
Run comprehensive 3-wave review against all source files in the repo, producing a prioritized issue backlog. Use for "full repo review", "review entire repo", "codebase health check", "review all files", "full codebase review". Do NOT use for PR-scoped reviews (use comprehensive-review) or single-concern reviews (use individual agents).
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.
Hugo site link health analysis: scan markdown, build internal link graph, validate paths, and report issues. Use when auditing site link structure, finding orphan pages, checking for broken internal/external links, or validating image paths. Use for "link audit", "orphan pages", "broken links", "link health", or "site link structure". Do NOT use for single-post pre-publish checks or content editing.
Build PromQL, LogQL, TraceQL queries for Perses panels. Validate query syntax, suggest optimizations, handle variable templating with Perses interpolation formats. Integrates with prometheus-grafana-engineer for deep PromQL expertise. Use for "perses query", "promql perses", "logql perses", "perses panel query". Do NOT use for datasource configuration (use perses-datasource-manage).