Creates a new Claude Code Skill following best practices. Use when the user wants to create a new skill, add a skill, or asks about writing skills for Claude Code. Fetches latest documentation before generating skill content. New skill. Create a skill.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Creates a new Claude Code Skill following best practices. Use when the user wants to create a new skill, add a skill, or asks about writing skills for Claude Code. Fetches latest documentation before generating skill content. New skill. Create a skill.
allowed-tools
Read, Grep, Glob, WebFetch, Write
Creating a New Skill
Follow this workflow when creating a new Claude Code Skill.
0) Fetch latest best practices (REQUIRED)
Before writing any skill content, you MUST fetch and read the latest documentation:
Use WebFetch to retrieve these pages and extract key guidelines before proceeding.
1) Check if skill should merge into existing skill (REQUIRED)
Before creating a new skill, first check if the content belongs in an existing skill.
Review existing skills
ls -la .claude/skills/
Decision criteria for merging
MERGE into existing skill as a rule if:
Topic is closely related to an existing skill's domain
Content would be a sub-topic of an existing skill
Similar workflows or patterns already exist
Adding as a rule keeps related knowledge together
CREATE new skill if:
Topic is distinct and doesn't fit any existing category
Content is substantial enough to warrant standalone skill
Different trigger keywords and use cases
Would make existing skill too large or unfocused
Token optimization considerations
When to split existing skills:
Skills should be split when they become too large, causing unnecessary token consumption on every load. Use these criteria:
🚨 SPLIT if any of these apply:
File size: Reference file >10 KB or >1000 lines
Usage frequency mismatch: Topics used in very different scenarios
Independent workflows: Topics don't share common patterns
Specific trigger words: Topic has distinct keywords that rarely overlap
✅ KEEP TOGETHER if:
High correlation: Topics frequently used together (>50% overlap)
Shared concepts: Common patterns, terminology, or workflows
Small files: All reference files <5 KB each
Natural grouping: User thinks of topics as related
Token savings formula:
Token Savings = (Skill_Size × Probability_Not_Needed) - Split_Overhead
Where:
- Skill_Size: Total tokens in skill (SKILL.md + all references)
- Probability_Not_Needed: % of tasks that don't need this topic
- Split_Overhead: ~500-1000 tokens (new SKILL.md + metadata)
Real-world examples from our codebase:
Original
Size
Split Into
Token Savings
1k-coding-patterns
15 KB (9 files)
6 focused skills
47-53% in 90% cases
1k-dev-workflows
43 KB (3 files)
3 focused skills
80% when not doing Sentry
Splitting strategies:
Conservative split (safe, minimal disruption):
Split only the largest, most independent file
Keep related topics together
Example: Split 34 KB Sentry analysis from 43 KB workflows
