skill-builder
Creates, refines, and validates Agent Skills following the open standard at agentskills.io, Claude Code extensions, and Anthropic best practices. Use when building, creating, generating, or designing new skills.
What this skill does
# Skill Builder
## Purpose
Creates production-ready Agent Skills following the official specifications
and best practices.
## When I Activate
I automatically load when you mention:
- "build a skill" or "create a skill"
- "generate a skill" or "make a skill"
- "design a skill" or "new skill"
## Authoritative References (Read These First)
Before creating any skill, read the current versions of these docs:
1. **Agent Skills Specification** (the open standard):
https://agentskills.io/specification
2. **Skill Authoring Best Practices** (Anthropic):
https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices
3. **Claude Code Skills Documentation** (Claude Code extensions):
https://docs.claude.com/en/docs/claude-code/skills
4. **Example Skills** (reference implementations):
https://github.com/anthropics/skills
These are the source of truth. If anything in this skill contradicts those
docs, the official docs win.
## What I Do
Create skills in 5 steps:
1. **Clarify** → Define purpose, scope, activation keywords
2. **Design** → Plan structure, decide on progressive disclosure
3. **Generate** → Create SKILL.md with proper frontmatter and body
4. **Validate** → Check against spec and best practices
5. **Test** → Verify activation and behavior
## Frontmatter (Agent Skills Spec)
Only two fields are required:
```yaml
---
name: my-skill
description: What this skill does and when to use it. Include specific keywords for discovery.
---
```
Optional fields: `license`, `compatibility`, `metadata`, `allowed-tools`.
Claude Code adds: `disable-model-invocation`, `user-invocable`, `model`,
`context`, `agent`, `hooks`, `argument-hint`.
**Do NOT use**: `version` (use `metadata.version`), `auto_activates`,
`priority_score`, `source_urls`, `evaluation_criteria`, `invokes`,
`philosophy`, `maturity` — none of these are recognized by any runtime.
## Key Best Practices
From the [official best practices](https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices):
### Conciseness
- Claude is already smart. Only add context it doesn't have.
- Challenge every paragraph: "Does this justify its token cost?"
- SKILL.md body under 500 lines.
### Description Quality
- Write in **third person** ("Processes Excel files", not "I help you")
- Include both what the skill does AND when to use it
- Include specific trigger keywords for discovery
- Max 1024 characters
### Progressive Disclosure
- Metadata loaded at startup (name + description only)
- SKILL.md loaded when skill activates
- Supporting files loaded only when needed
- Keep references **one level deep** from SKILL.md
### Degrees of Freedom
- **High freedom**: Multiple valid approaches, context-dependent
- **Medium freedom**: Preferred pattern exists, some variation OK
- **Low freedom**: Fragile operations, exact sequence required
### No Time-Sensitive Content
- Never write "as of today", "recently added", "new in v3.0"
- Use an "old patterns" section for historical context if needed
### Feedback Loops
- Run validator → fix errors → repeat
- Include verification steps for critical operations
## Validation Checklist
✅ **Frontmatter**: `name` and `description` present and valid
✅ **Name**: Lowercase, hyphens only, 1-64 chars, matches directory name
✅ **Description**: 1-1024 chars, third person, includes trigger keywords
✅ **Body**: Under 500 lines
✅ **References**: One level deep from SKILL.md
✅ **No stale content**: No temporal references
✅ **Consistent terminology**: One term per concept throughout
✅ **Tested**: Works with at least 3 representative prompts
## Supporting Files
- [reference.md](./reference.md): Detailed patterns, architecture, validation rules
- [examples.md](./examples.md): Skill creation workflows and examples
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.