Loading...
Loading...
Found 2,589 Skills
Create a new voice profile from writing samples. 7-phase pipeline: Collect, Extract, Pattern, Rule, Generate, Validate, Iterate. Wabi-sabi (natural imperfections as features) is the core principle. Use when creating a new voice, starting voice calibration, or building a voice profile from scratch. Use for "create voice", "new voice", "build voice", "voice from samples", "calibrate voice". Do NOT use for generating content in an existing voice (use voice-orchestrator), editing content (use anti-ai-editor), or comparing voices (use voice-calibrator compare mode).
Defense-in-depth verification before declaring any task complete. Run tests, check build, validate changed files, verify no regressions. Applies 4-level adversarial artifact verification (EXISTS > SUBSTANTIVE > WIRED > DATA FLOWS) with goal-backward framing. Use before saying "done", "fixed", or "complete" on any code change. Use for "verify", "make sure it works", "check before committing", or "validate changes". Do NOT use for debugging (use systematic-debugging) or code review (use systematic-code-review).
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).
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.
Fetch PR feedback from all GitHub sources and validate every comment before acting. Use when user needs to process PR review comments, address reviewer feedback, or triage pull request discussions. Use for "review comments", "PR feedback", "address reviews", "address feedback", or "what did reviewers say". Do NOT use for creating new PRs, code review of local changes, or general code analysis without an existing PR.
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.
Review existing Perses dashboards for quality: fetch via MCP or API, analyze panel layout, query efficiency, variable usage, datasource configuration. Generate improvement report. Optional --fix mode. 4-phase pipeline: FETCH, ANALYZE, REPORT, FIX. Use for "review perses dashboard", "audit dashboard", "perses dashboard quality". Do NOT use for creating new dashboards (use perses-dashboard-create).
Reusable workflow for implementing and validating the RDS Button component using @rds-vue-ui packages from the private registry, including theme wiring, examples, and QA checks.
Use this skill whenever the user mentions IP geolocation feeds, RFC 8805, geofeeds, or wants help creating, tuning, validating, or publishing a self-published IP geolocation feed in CSV format. Intended user audience is a network operator, ISP, mobile carrier, cloud provider, hosting company, IXP, or satellite provider asking about IP geolocation accuracy, or geofeed authoring best practices. Helps create, refine, and improve CSV-format IP geolocation feeds with opinionated recommendations beyond RFC 8805 compliance. Do NOT use for private or internal IP address management — applies only to publicly routable IP addresses.
Start and monitor workflows via WorkflowClient with strict input variable matching.
Sync design tokens between code and Figma variables with strict drift reporting, mandatory approval gate, safe delta apply, and persisted reports.
Static analysis checklist for backend PRs (NestJS/TypeScript) — B1–B21 runtime bugs, logic errors, silent failures, test correctness. Use when you want to check for bugs only. For the full review workflow, use pr-review.