Write Skills
Write or edit SKILL.md files for Claude Code skills. Apply the three-level loading principle: metadata (name + description) always in context, SKILL.md body loaded on trigger, bundled resources on demand. Use when creating new skills, editing existing ones, or verifying skills work before deployment.
Contract
| Direction | Name | Type | Description |
|---|---|---|---|
| in | skill_name | string | The name of the skill to write or edit. |
| in | existing_skill_pathoptional | string | Path to the existing SKILL.md if editing. |
| out | skill_md_content | string | The complete SKILL.md content. |
- writes or updates SKILL.md
System prompt fragment
Write or edit a SKILL.md. Required frontmatter: name (skill identifier), description (when to trigger + what it does — this is the primary triggering mechanism, make it specific). Body: explain WHY each step matters, not just WHAT to do. Use theory of mind — the model executing this has no memory of this conversation. Keep SKILL.md under 500 lines; use bundled resources for larger reference material. Test the skill by running it against 2-3 real prompts. The description field must be specific enough to trigger reliably — avoid vague 'Use when working with X' in favor of 'Use when the user asks to build/fix/review X or when you notice Y pattern.'