agent-architect
Claude Code architecture advisor. Classifies knowledge and delegates to appropriate skills. Use when deciding where to put new knowledge or restructuring components.
shared-world
Maintain a wiki-style world bible for collaborative fiction. Use for long-running story worlds, shared universes, membership sites, or any fiction requiring persistent canonical reference.
resource-search
Search and collect the latest Skills resources including blog posts, GitHub repositories, video tutorials, case studies, and tools. Focus on Skills development, SKILL.md examples, and Skills best practices. Use when searching for new Skills resources, updating the resource library, or when the user asks to find Skills-related content.
08-mofa-studio-reference
Troubleshooting and operational reference for MoFA Studio: common errors, Dora issues, Makepad pitfalls, and checklists. Use when debugging or validating fixes.
tzurot-docs
Documentation maintenance for Tzurot v3 - Updating CURRENT_WORK.md, folder structure, and keeping docs current. Use at session end or when documentation needs updating.
discussion-commenter
Post Q&A entries from office hours writeups as comments to a GitHub Discussion. Use when the user wants to post writeup content to a discussion thread.
write-claude-md
Create effective CLAUDE.md files with proper constitution using <law> blocks. Use when creating project setup, writing new CLAUDE.md, or improving existing configuration.
observation
Access accumulated observations about patterns, behaviors, and the world. Contains observations about E, the environment, recurring patterns, and insights from ongoing experience. Use when asked about patterns noticed, behavioral observations, or accumulated understanding. Triggers: what have I noticed, patterns, observations, observed that, tend to.
gsc-assistant
Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.
obsidian-vault-intelligence
Use when working with Obsidian vault via MCP - covers effective search patterns, note operations, intelligent queries, and cross-reference strategies for knowledge extraction
searxng-search
Enhanced web and package repository search using local SearXNG instance
preventionpatterns
Known bug patterns and their fixes to prevent regression.
root-cause
Dig to fundamental truths and real causes behind problems. Use when user asks "why does this happen", "what's the real problem", "root cause", "first principles", "jobs to be done", "JTBD", "five whys", "fundamental reason", or needs to understand underlying causes rather than symptoms.
tech-debt-prioritizer
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".
braiins-os
Comprehensive Braiins OS skill covering API, feeds, and documentation
outline-coach
Act as an assistive outline coach who guides structural development through questions. Use when helping someone develop their own outline through diagnosis and frameworks. Critical constraint - never generate outline content. Instead ask questions, identify structural issues, suggest approaches, and let the writer structure.
technical-specification
Build validated specifications from source material through collaborative refinement. Use when: (1) User asks to create/build a specification from source material, (2) User wants to validate and refine content before planning, (3) Converting source material (discussions, research, requirements) into standalone specifications, (4) User says 'specify this' or 'create a spec', (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in docs/workflow/specification/{topic}.md that can be used to build implementation plans.
github-issue-creator
Create well-structured GitHub issues focused on user problems and outcomes, not implementation. Use when user reports bugs or requests features to ensure clear, testable requirements without premature implementation details.
skill-architect
Analyzes the codebase to identify areas that would benefit from specialized skills, reviews existing skills for gaps, and creates new skills with user approval. Use when the user wants to improve their skill coverage, create new code review skills, or ensure all major components have appropriate specialized assistants. Proactively suggests skills for undocumented areas like depot services, build systems, deployment workflows, or testing infrastructure.
