Loading...
Loading...
Found 149 Skills
Go concurrency patterns and primitives: goroutines, channels, sync primitives, worker pools, rate limiting, context propagation. Use when writing concurrent Go code, implementing worker pools, fan-out/fan-in pipelines, rate limiters, or debugging race conditions and goroutine leaks. Triggers: goroutine, channel, sync.Mutex, sync.WaitGroup, worker pool, fan-out, fan-in, rate limit, concurrent, parallel, context.Context, race condition, deadlock. Do NOT use for sequential Go code, general Go syntax, error handling patterns, or HTTP routing without concurrency concerns.
Evidence-based 4-phase root cause analysis: Reproduce, Isolate, Identify, Verify. Use when user reports a bug, tests are failing, code introduced regressions, or production issues need investigation. Use for "debug", "fix bug", "why is this failing", "root cause", or "tests broken". Do NOT use for feature requests, refactoring, or performance optimization without a specific bug symptom.
Data engineering patterns for ETL pipelines, data warehousing, Apache Spark, and data quality validation
Deterministic 4-phase documentation drift detector: Scan, Cross-Reference, Detect, Report. Use when skills/agents/commands are added, removed, or renamed, when README files seem outdated, or before committing documentation changes. Use for "check docs", "sync README", "documentation audit", or "stale entries". Do NOT use for writing documentation content, improving descriptions, or generating new README files.
Grafana-to-Perses dashboard migration: export Grafana dashboards, convert with percli migrate, validate converted output, fix incompatibilities, deploy to Perses. Handles bulk migration with parallel processing. Use for "migrate grafana", "grafana to perses", "perses migrate", "convert grafana". Do NOT use for creating new dashboards from scratch (use perses-dashboard-create).
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).
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).
Fish shell configuration: config.fish, functions, abbreviations, variable scoping, conf.d modules, and PATH management. Use when user's $SHELL is fish, editing .fish files, working in ~/.config/fish/, or migrating from Bash. Use for "fish config", "fish function", "abbr", "conf.d", "fish_add_path", or "funcsave". Do NOT use for Bash/Zsh-only scripts, POSIX shell portability, or non-shell configuration tasks.
Safe bulk editing across multiple Hugo markdown posts: find/replace, frontmatter updates, content transforms with mandatory preview before apply. Use when user needs batch text replacement, bulk frontmatter field changes, heading/link/whitespace normalization, or regex-based content transforms across posts. Use for "batch edit", "find and replace across files", "add field to all posts", "bulk update tags". Do NOT use for single-file edits, structural refactoring, or content generation.
Validate Perses resources: run percli lint locally or with --online against a server. Check dashboard definitions, datasource configs, variable schemas. Report errors with actionable fixes. Use for "perses lint", "validate perses", "check dashboard", "perses validate". Do NOT use for plugin schema testing (use perses-plugin-test).
RED-GREEN-REFACTOR testing for agents: dispatch subagents with known inputs, capture verbatim outputs, verify against expectations. Use when creating, modifying, or validating agents and skills. Use for "test agent", "validate agent", "verify agent works", or pre-deployment checks. Do NOT use for feature requests, simple prompt edits without behavioral impact, or agents with no structured output to verify.
Perses variable lifecycle management: create Text and List variables at global, project, or dashboard scope. Handle variable chains with dependencies (A depends on B depends on C). Supports 14+ interpolation formats. Uses MCP tools when available, percli CLI as fallback. Use for "perses variable", "dashboard variable", "perses filter", "add variable". Do NOT use for datasource management (use perses-datasource-manage).