moai
Core Claude Code extension-authoring playbook for skills, agents, commands, plugins, hooks, and settings. Use when creating or reviewing Claude Code extensions and automation workflows.
What this skill does
# Claude Code Authoring Foundation Use this skill as the default foundation for extension work in this repo. ## When to use - Building or refactoring a `SKILL.md` - Creating or tightening an agent file in `claude/agents/` - Creating plugin scaffolding or command packs - Reviewing hook configuration and permission boundaries - Migrating verbose docs to compact progressive-disclosure structure ## Fast workflow <workflow> 1. Classify task: skill, agent, plugin, command, hook, or settings. 2. Load only required references from `reference/README.md`. 3. Implement smallest working change with least-privilege tools. 4. Validate: lint/tests/command checks relevant to touched files. 5. Summarize changes, risk, and follow-up work. </workflow> ## Authoring rules ### Skills - Keep frontmatter minimal and valid. - Description must answer: what it does, when to use it, trigger phrases. - Keep `SKILL.md` concise; move long examples to one-hop reference files. - Do not embed copied vendor docs; use short summaries plus canonical links. - Prefer deterministic checklists/workflows over long prose. ### Agents - One-sentence mission. - Explicit constraints and tool boundaries. - Output contract with clear deliverables. - Avoid repeated global policy text already covered in shared docs. ### Commands and plugins - Keep command interfaces explicit and small. - Use argument placeholders consistently (`$ARGUMENTS`, `$1`, `$2`). - In plugins, keep manifest/tool scopes tight and document required setup only. ### Hooks and safety - Use hooks for policy enforcement, not noisy logging. - Never log secrets. - Fail with actionable messages when blocking. ## Token efficiency checklist - Is this instruction duplicated elsewhere? - Can a table replace paragraphs? - Can examples be reduced to one representative pattern? - Can a local copy of docs be replaced with a URL? - Can this be verified by a script or command? ## Output format When this skill drives work, return: 1. Scope and assumptions 2. Files changed 3. Validation performed 4. Residual risks and next steps ## Resources - `../AGENT_SKILL_SPEC.md` - Anthropic and Copilot alignment baseline - `reference/README.md` - canonical link map and local standards - `examples.md` - compact implementation templates
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.