Loading...
Loading...
Found 3,352 Skills
Use when about to ask the user a factual question, propose a solution, diagnose an error, or choose between approaches. Triggers on: 'Do you have X installed?', 'What version?', 'Is X configured?', 'We should...', 'The fix is...', 'Options: 1...', 'Based on my understanding...', 'I believe X supports...'. Before deciding anything, spin up parallel subagents to WebSearch for current docs, community solutions, framework best practices, and GitHub issues. Your memory is stale — verify everything.
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album concept.
Use when parameter values appear in multiple documents and consistency must be verified, especially for quantitative values that may differ due to measurement context or require reconciliation
MANDATORY before starting any task. Enforces the GPA execution loop that prevents tool call sprawl. G: GATHER phase combines discover queries + memory reads + file reads into one phase. P: Plan in text with zero tool calls. A: APPLY all writes/edits/verification in one phase. One call per tool type per phase — batch all same-type operations together. Covers dependency analysis, batch opportunities, scope estimation, and loop-back triggers.
Use when substantive documents (reviews, analyses, synthesis documents) need adversarial review to strengthen arguments, identify weak points, and challenge assumptions before editorial polish (mandatory for Writer → Devil's Advocate pairing protocol)
Use when research direction needs assessment, critical knowledge gaps must be identified, or priorities must be recommended based on impact, dependencies, and effort (especially at project milestones or when scope questions arise)
Use this skill when the user asks to "create a finding", "record an insight", "what findings exist", "show findings", or wants to create or review evidence-backed analysis insights from crawl observations. Creates and queries curated findings with evidence chains.
Use when coordinating multi-agent work with dependencies, parallel workstreams, or complex handoffs requiring milestone tracking
8-agent QA loop: browser exploration via Playwright MCP, then analyze, plan, test, audit, heal, expand, snapshot. Quality gate score >= 85 to pass.
Identifies bugs, analyzes errors, performs root cause analysis, and proposes fixes
Researches project histories, changelogs, developer interviews, and open source documentation. Use when the album subject involves technology projects or developer stories.
General guidance for building Rust CLI programs (clap/anyhow/tracing/serde_json), with agent-friendly patterns: JSON output mode, stdout/stderr separation, predictable exit codes, integration testing, and a cargo-release based release workflow.