skill-creator
Create new Claude Code skills following SOTA compact design patterns (v3.2)
When & Why to Use This Skill
The Skill Creator is a specialized developer tool designed to automate the generation of high-performance Claude Code skills. By implementing State-of-the-Art (SOTA) compact design patterns (v3.2), it solves the problem of inefficient, context-heavy agent instructions. It streamlines the creation of reusable workflows, ensuring that skill definitions remain ultra-compact while deferring complex documentation to on-demand files, which optimizes token usage and improves agent responsiveness.
Use Cases
- Standardizing Team Workflows: Automatically generate structured SKILL.md files for recurring development tasks to ensure consistent agent behavior across a team.
- Optimizing Agent Context: Refactor existing, verbose Claude skills into SOTA-compliant compact versions to minimize context window clutter and reduce latency.
- Modular Documentation Management: Create scalable skill packages that include optional EXAMPLES.md and GUIDE.md files, which are only loaded when the agent encounters complex edge cases.
- Rapid Prototyping of Agentic Tools: Quickly transform a manual multi-step process into a formal Claude Code skill with built-in design checks for justification and reusability.
| name | skill-creator |
|---|---|
| description | Create new Claude Code skills following SOTA compact design patterns (v3.2) |
| version | 1.0.0 |
Skill Creator - SOTA Pattern
Workflow
Gather requirements: Ask user for skill purpose, trigger conditions, and key workflow steps
Design check: Ensure skill is justified (not a simple task, needs reusability)
Create structure:
~/.claude/skills/[skill-name]/SKILL.md(compact, <200 words)~/.claude/skills/[skill-name]/EXAMPLES.md(optional, loaded only on demand)~/.claude/skills/[skill-name]/GUIDE.md(optional, loaded only on demand)
Generate SKILL.md following SOTA pattern:
- YAML frontmatter: name, description, version
- Clear workflow (numbered steps)
- Try-first approach (don't read configs unnecessarily)
- Lazy loading (load details only when needed)
- Key principle statement
- Optional: "See EXAMPLES.md" or "See GUIDE.md" (but don't auto-load)
Create optional docs only if skill is complex:
- EXAMPLES.md: Detailed usage examples
- GUIDE.md: Advanced patterns, troubleshooting, edge cases
Update skill registry: Add to
~/.claude/skills/README.mdif exists
SOTA Design Principles
Target: <200 words in SKILL.md Pattern: Try operations first, handle errors gracefully Loading: Lazy load everything (even docs) Config: Don't read unless absolutely necessary Separation: Examples/guides in separate files, loaded only when needed
Key Principle
Skills are for recurring workflows, not one-off tasks. Minimize context by keeping SKILL.md ultra-compact and deferring all details to optional, on-demand files.
Optional docs: EXAMPLES.md, GUIDE.md (load manually when needed)