Find the perfect capability for your agent.
Analyze whether your response addresses the actual question asked before posting. Use when: (1) About to post response to forum/Slack question, (2) Want to validate response coverage, (3) Need to ensure solving the right problem, (4) Want specific improvement suggestions for gaps in response
Search for items and properties on Wikidata and retrieve external identifiers. Use when an agent needs to (1) search for Wikidata items by label or alias, (2) get entity details including labels, descriptions, aliases, (3) retrieve external identifiers (authority control IDs) for an entity, (4) look up properties or claims for items. Triggers on queries mentioning Wikidata, Q-IDs, P-IDs, authority control, external identifiers, or structured knowledge base lookups.
Multi-source comprehensive research using claude-researcher and gemini-researcher agents. Three modes - Quick (3 agents), Standard (9 agents), Extensive (24 agents with be-creative skill). USE WHEN user says 'do research', 'quick research', 'extensive research', 'find information about', 'investigate', 'analyze trends', 'current events', or any research-related request.
Write and maintain an implementation diary: step-by-step narrative of what changed, why, what worked, what failed (with exact errors/commands), what was tricky, and how to review/validate. Use when a user asks to create/update a “Diary” doc, record work for a ticket, document debugging outcomes, or produce code review instructions and future follow-ups.
Perform a repo-wide, evidence-based audit of documentation against the current codebase and recent changes. Produces a proposed, fully rewritten documentation set in TempDoc-ForUserReview and asks for approval before any changes are applied to the existing docs.
Research and document new parasites, cleanup locations, and hidden data. Use when asked to add a parasite, discover zombie processes, research app persistence, add cleanup locations, or run iterative discovery loops (Ralph Wiggum). Handles all knowledge base modifications.
Comprehensive guide to writing clear, helpful, and user-friendly error messages that guide users to solutions
This skill should be used when the user asks to "write docs", "create documentation", "document this project", "write a README", or wants to create comprehensive documentation from scratch. Spawns @writer agent to analyze codebase and create consolidated docs.
Use this skill when reading or updating wiki pages on skyline.ms.
This skill should be used when the user asks "where is X", "how does X work", "explain X", "show me the architecture", "find component", "what handles X", or references C3 IDs (c3-0, c3-1, adr-*). Requires .c3/ to exist. For changes, route to c3-alter instead.
General reference documents by domain. Use when creating architecture docs, strategy documents, specs, or guides.
Debug frontend issues using Chrome DevTools MCP. Find root causes of UI bugs, console errors, network failures, DOM problems. Use when user mentions "debug", "fix bug", "troubleshoot", "not working", "error", "console", or has UI/DOM/network issues.
Root cause fixing and avoiding workarounds. Use when encountering errors, bugs, or problems. Triggers on "bug", "error", "fix", "debug", "workaround", "wrapper", "hack", "broken", "not working", "failing", "issue", or when tempted to add complexity to avoid fixing the real problem.
Explain code in plain English with visual diagrams. Use when user wants to understand how code works or needs documentation.
Write Python docstrings following PEP 257 and popular formats (Google, NumPy, Sphinx). WHEN: Writing docstrings for Python functions/classes/modules, choosing docstring format, documenting parameters/returns/exceptions. WHEN NOT: JavaScript documentation (use js-docstring), TypeScript (use ts-docstring), PHP (use php-docstring), general code comments.
Documentation-first development methodology. The goal is AI-ready documentation - when docs are clear enough, code generation becomes automatic. Triggers on "Build", "Create", "Implement", "Document", or "Spec out". Version 3.4 adds complete 13-item Clarity Gate with scoring rubric and self-assessment.
Generate detailed API contracts and specifications including OpenAPI/Swagger definitions, endpoint documentation, and integration guidelines
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Autonomous documentation maintainer that ensures code changes are reflected in documentation
