| name | skill-creator |
| description | Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. |
Skill Creator
This skill provides guidance for creating effective skills.
About Skills
Skills are modular, self-contained packages that extend Claude's capabilities by providing
specialized knowledge, workflows, and tools.
What Skills Provide
- Specialized workflows - Multi-step procedures for specific domains
- Tool integrations - Instructions for working with specific file formats or APIs
- Domain expertise - Project-specific knowledge, schemas, business logic
- Bundled resources - Scripts, references, and assets for complex and repetitive tasks
Core Principles
Concise is Key
Default assumption: Claude is already very smart. Only add context Claude doesn't already have. Prefer concise examples over verbose explanations.
Set Appropriate Degrees of Freedom
High freedom: When multiple approaches are valid.
Medium freedom: When a preferred pattern exists with acceptable variation.
Low freedom: When operations are fragile and consistency is critical.
Anatomy of a Skill
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter (name + description)
│ └── Markdown instructions
└── Bundled Resources (optional)
├── scripts/ - Executable code
├── references/ - Documentation loaded as needed
└── assets/ - Files used in output
Progressive Disclosure
- Metadata (name + description) - Always in context (~100 words)
- SKILL.md body - When skill triggers (<5k words)
- Bundled resources - As needed by Claude
Keep SKILL.md body under 500 lines. Split content into separate files when approaching this limit.
Skill Creation Process
- Understand the skill with concrete examples
- Plan reusable skill contents (scripts, references, assets)
- Create the skill directory structure
- Edit the skill (implement resources and write SKILL.md)
- Iterate based on real usage
Reference Files
SKILL.md Writing Guidelines
Frontmatter
name: The skill name
description: What the skill does AND when to use it. Include all trigger information here.
Body
Write instructions for using the skill and its bundled resources. Use imperative/infinitive form.
What NOT to Include
- README.md, CHANGELOG.md, or auxiliary documentation
- Setup and testing procedures
- User-facing documentation beyond SKILL.md