Loading...
Loading...
Found 149 Skills
Verify Claude Code Toolkit installation, diagnose issues, and guide new users through first-time setup
Detect and remediate Go anti-patterns: premature interface abstraction, goroutine overkill, context soup, error wrapping mistakes, generic abuse, channel misuse, unnecessary function extraction, and interface pollution. Use when reviewing Go code for quality, detecting over-engineering, or when user mentions "anti-pattern", "code smell", "Go mistake", or "bad Go". Do NOT use for feature implementation, performance optimization without a code smell, or non-Go languages.
Generate and validate Git branch names from commit messages or descriptions. Use when creating branches, generating names for /pr-sync, validating existing branch names, or converting conventional commits to branch prefixes. Triggers: "branch name", "create branch", "name this branch", "validate branch". Do NOT use for git operations (checkout, merge, delete), branching strategies, or branch protection rules.
SAP Converged Cloud Go coding conventions extracted from sapcc/keppel and sapcc/go-bits PR reviews. Enforces architecture patterns, library usage rules, error handling conventions, testing patterns, and anti-over-engineering principles. Use when working in sapcc/* repos, when code imports github.com/sapcc/go-bits, or when targeting SAP CC code review standards. Do NOT use for general Go projects without sapcc dependencies.
Validate a published or draft-preview WordPress post in a real browser using Playwright. Checks rendered title, heading structure, image loading, OG/meta tags, JavaScript errors, and responsive layout at mobile/tablet/desktop breakpoints. When Chrome DevTools MCP is available, can use it for live browser inspection as an alternative to Playwright. Use for "validate wordpress post", "check live post", "verify published post", "wordpress post looks right", "check og tags", or "responsive check wordpress". Do NOT use for source markdown validation (use pre-publish-checker), SEO keyword analysis (use seo-optimizer), or uploading content (use wordpress-uploader).
Guided Perses dashboard creation: gather requirements (metrics, datasource, layout), generate CUE definition or JSON spec, validate with percli lint, deploy with percli apply or MCP perses_create_dashboard. Use when user wants to create a new Perses dashboard, build a monitoring dashboard, or generate dashboard definitions. Use for "create perses dashboard", "new dashboard", "perses new dashboard", "build dashboard". Do NOT use for Grafana migration (use perses-grafana-migrate) or plugin development (use perses-plugin-create).
Systematic 6-phase analysis of external repositories for ideas worth adopting: clone, parallel deep-read, self-inventory, synthesize gaps, targeted audit of affected subsystems, reality-grounded report. Use when evaluating whether an external repo provides value, analyzing repos for useful patterns, or comparing approaches. Do NOT use for general codebase exploration (use explore-pipeline instead).
Deterministic 3-phase service health monitoring: Discover, Check, Report. Use when user asks about service status, process health, uptime, or whether services are running. Use for "health check", "is service up", "service status", "what's running", or "check if alive". Do NOT use for HTTP endpoint validation, performance profiling, or log analysis without a specific health concern.
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.
DAG-based multi-skill orchestration: Discover, Plan, Validate, Execute. Builds execution graphs for tasks requiring multiple skills in sequence or parallel with dependency resolution and context passing. Use when a task requires 2+ skills chained together, parallel skill execution, or conditional branching between skills. Use for "compose skills", "chain workflow", "multi-skill", or "orchestrate skills". Do NOT use when a single skill can handle the request, or for simple sequential invocation that needs no dependency management.
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
Restore session state from handoff artifacts and route to the next action. Priority cascade: HANDOFF.json (highest) > .continue-here.md > incomplete task_plan.md > git log. Presents a status dashboard, then executes the next action. Use for "resume", "continue", "pick up where I left off", "what was I doing", "continue work". Do NOT use for starting new tasks (use /do), reviewing past sessions (use /retro), or reading task plans (read task_plan.md directly).