Loading...
Loading...
Found 2,611 Skills
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.
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).
Pre-publication validation for Hugo posts: front matter, SEO, links, images, draft status, and taxonomy. Use when user wants to check a post before publishing, validate blog content, or run pre-publish checks. Use for "pre-publish", "check post", "ready to publish", "validate post", or "publication check". Do NOT use for content writing, editing prose, or generating new posts.
Audit and maintain blog taxonomy (categories/tags) for consistency, SEO, and navigation: scan content, detect orphans and duplicates, merge and rename terms, verify builds. Use when user asks to "audit tags", "fix taxonomy", "consolidate categories", "merge tags", or "clean up taxonomy". Do NOT use for writing new content, individual post SEO optimization, or major content restructuring.
4-phase code review methodology: UNDERSTAND changes, VERIFY claims against code, ASSESS security/performance/architecture risks, DOCUMENT findings with severity classification. Use when reviewing pull requests, auditing code before release, evaluating external contributions, or pre-merge verification. Use for "review PR", "code review", "audit code", "check this PR", or "review my changes". Do NOT use for writing new code or implementing features.
Non-destructive 4-phase image validation: Discover, Validate, Analyze, Report. Use when auditing web images for accessibility, broken references, oversized files, or format mismatches. Use for "image audit", "check alt text", "find broken images", "optimize images", or "page weight". Do NOT use for image creation, editing pixels, CDN configuration, or automated image conversion without explicit user consent.
Run Vitest tests and parse results into actionable output. Use WHEN user needs to run JavaScript/TypeScript tests in a Vitest-configured project, verify test suites pass, or get structured failure reports. Use for "run tests", "vitest", "check if tests pass", or "test results". Do NOT use for Jest/Mocha projects, installing dependencies, writing new tests, or auto-fixing failing assertions.
Deterministic API endpoint validation with structured pass/fail reporting. Use when endpoints need smoke testing, health checks are required before deployment, or CI/CD pipelines need HTTP validation gates. Use for "validate endpoints", "check api health", "api smoke test", or "are endpoints working". Do NOT use for load testing, browser testing, full integration suites, or OAuth/complex authentication flows.
Gold-standard code review for SAP CC Go repositories against the project's lead review standards. Dispatches 10 domain-specialist agents in parallel — each loads domain-specific references and scans ALL packages for violations in their assigned domain. Produces a prioritized report with REJECTED/CORRECT code examples. Optional --fix mode applies corrections on a worktree branch. This is the definitive "would this code pass lead review?" assessment.
Deterministic audit of cron/scheduled job scripts for reliability, error handling, logging, cleanup, and concurrency safety. Use when user says "audit cron", "check cron script", "cron best practices", "scheduled job review", or "bash script audit". Do NOT use for crontab scheduling syntax, systemd timers, or general shell linting without a cron/scheduled-job context.
Spawn 10 independent parallel agents to analyze source material from distinct perspectives, synthesize findings, and apply improvements to a target agent or skill. Use when source material is complex and multi-angle extraction justifies 3-5x token cost over inline analysis. Use for "parallel analysis", "multi-perspective", or "deep extraction". Do NOT use for routine improvements, simple source material, or when token budget is limited.
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.