create-skill · siviter-xyz — Claude Code skill: write your own skills
A skill that walks the agent through building other skills: SKILL.md layout, the 200-line rule, and moving detail into references.
npx skills add siviter-xyz/dot-agent --skill create-skill -a claude-codeWhat create-skill does
create-skill is a skill about skills. It hands the agent a method for progressive disclosure: metadata stays in context, the SKILL.md body loads when the skill triggers, and heavier material sits in references/ until it is needed. The author puts numbers on it — an 85% cut in initial context load, activation dropping from 500ms+ to under 100ms.
The hard rule is that SKILL.md stays under 200 lines. If it does not fit, split the content out into references/. The folder layout is small: a required SKILL.md with YAML frontmatter (name and description), plus optional scripts/, references/ and assets/. There is a section on degrees of freedom too — plain text when several approaches are valid, parameterised scripts for the middle ground, fixed scripts for fragile operations.
A skill sits on top of a model, so how well it works depends on which model reads it. The author tells you to test against every model you plan to use, otherwise parts of the instructions may never fire. Four files in references/ carry the detail: progressive disclosure, the SKILL.md format, examples, and a best-practices guide.
What it helps with
- split an oversized SKILL.md into body and references
- decide between a text instruction and a parameterised script
- write frontmatter that makes the skill trigger at the right time
- shrink the context a skill occupies before activation
- test one skill across several models
Example prompts for the agent
- help me create a skill for our internal APIs
- rewrite this SKILL.md — it has grown too long, move the rest into references
- check my skill structure against the 200-line rule
How to install create-skill
1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill create-skill -a claude-code2Manually: put the files in place
~/.claude/skills/create-skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-skill/
1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill create-skill -a codex2Manually: put the files in place
.agents/skills/create-skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill create-skill -a cursor2Manually: put the files in place
.cursor/skills/create-skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install siviter-xyz/dot-agent create-skill2Manually: put the files in place
.github/skills/create-skill/SKILL.md1Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill create-skill -a gemini-cli2Platform CLI
gemini skills install https://github.com/siviter-xyz/dot-agent --path skills/create-skillManually: put the files in place
.devin/skills/create-skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add siviter-xyz/dot-agent --skill create-skill -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-skill
How do I install create-skill in Claude?
Run npx skills add siviter-xyz/dot-agent --skill create-skill -a claude-code. The skill file lands at ~/.claude/skills/create-skill/SKILL.md.
What does create-skill do?
It gives the agent instructions for authoring skills: folder structure, frontmatter, the 200-line rule, and pushing detail into references/.
Why does SKILL.md have to stay under 200 lines?
The body loads into context when the skill triggers, and every extra line costs tokens. Anything that does not fit should go into references/ files.
Source text
SKILL.md · MIT
---
name: create-skill
description: Guide for creating effective skills following best practices. Use when creating or updating skills that extend agent capabilities.
---
# Create Skill
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, and tool integrations.
## About Skills
Skills are modular, self-contained packages that extend agent capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks.
### What Skills Provide
1. Specialized workflows - Multi-step procedures for specific domains
2. Tool integrations - Instructions for working with specific file formats or APIs
3. Domain expertise - Company-specific knowledge, schemas, business logic
4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
## Progressive Disclosure Principle
**The 200-line rule is critical.** SKILL.md must be under 200 lines. If you need more, split content into `references/` files.
### Three-Level Loading System
1. **Metadata (name + description)** - Always in context (~100 words)
2. **SKILL.md body** - When skill triggers (<200 lines, ideally <500 lines for optimal performance)
3. **Bundled resources** - As needed by agent (unlimited)
### Why Progressive Disclosure Matters
- 85% reduction in initial context load
- Activation times drop from 500ms+ to under 100ms
- Agent loads only what's needed, when it's needed
- Skills remain maintainable and focused
## Skill Structure
```
skill-name/
├── SKILL.md (required, <200 lines)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ └── description: (required)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code
├── references/ - Documentation loaded as needed
└── assets/ - Files used in output
```
## Core Principles
### Concise is Key
The context window is a shared resource. Your skill shares it with everything else the agent needs. Be concise and challenge each piece of information:
- Does the agent really need this explanation?
- Can I assume the agent knows this?
- Does this paragraph justify its token cost?
### Set Appropriate Degrees of Freedom
- **High freedom**: Text-based instructions for multiple valid approaches
- **Medium freedom**: Pseudocode or scripts with parameters
- **Low freedom**: Specific scripts with few/no parameters for fragile operations
### Test with All Models
Skills act as additions to models, so effectiveness depends on the underlying model. Test your skill with all models you plan to use it with.
## References
For detailed guidance, see:
- `references/progressive-disclosure.md` - 200-line rule and references pattern
- `references/skill-structure.md` - SKILL.md format and frontmatter details
- `references/examples.md` - Good skill examples
- `references/best-practices.md` - Comprehensive best practices guide
© siviter-xyz · MIT · siviter-xyz/dot-agent
Similar skills
All skills for Agent setup: memory, context, orchestration →create-skill by other authors comes first.