Loading...
Loading...
Found 3,068 Skills
You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
Use when reviewing SKILL.md files for structure and trigger quality.
Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug.
Check if a newer version of groove is available on GitHub.
Audits document semantic content against stated SCOPE and project goals. Checks coverage, off-topic content, SSOT. File-based report with scope_alignment score.
SvelteKit full-stack Svelte framework. Covers routing, load functions, form actions, and server-side rendering. Use when building SvelteKit applications. USE WHEN: user mentions "SvelteKit", "Svelte Kit", asks about "+page.svelte", "load functions", "form actions in SvelteKit", "SvelteKit routing", "use:enhance", "hooks.server.ts", "SvelteKit adapters" DO NOT USE FOR: Svelte without SvelteKit - use `frontend-svelte` instead; Next.js - use `nextjs-app-router` instead; Nuxt - use `nuxt3` instead; Remix - use `remix` instead
Run browser tests on pages affected by current PR or branch
Audit and sync AI agent configuration files (CLAUDE.md, CODEX.md, AGENTS.md, .cursorrules, hooks, settings) across workspaces. Use when agent configs drift, rules duplicate, files go stale, or after workspace restructuring.
Audit PostHog survey SDK features and version requirements
Run a comprehensive data quality assessment and produce a scorecard across 6 dimensions: completeness, uniqueness, consistency, timeliness, accuracy, validity. Use when the user asks about data quality, mentions data issues, wants to audit a table, is onboarding a new data source, or needs to validate pipeline output.
Validate plans against 10 verification dimensions before execution begins. Uses goal-backward analysis to catch dropped requirements, vague tasks, missing dependencies, and scope overreach. Produces PASS/BLOCK verdict with structured findings. Use for "check plan", "validate plan", "is this plan ready", "review plan before executing", or "/plan-checker". Do NOT use for plan creation (use feature-plan or workflow-orchestrator) or plan lifecycle management (use plan-manager).
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).