creating-skills

---

name: creating-skills description: Create and refine Claude Code Skills. Use when creating skills, writing SKILL.md files, or improving existing skills.

<accessing_skill_files> When this skill is invoked, Claude Code provides the base directory in the loading message:

CopyBase directory for this skill: {skill_dir}

Use this path for all skill file access:

• References: {skill_dir}/references/
• Workflows: {skill_dir}/workflows/
• Templates: {skill_dir}/templates/
• Scripts: {skill_dir}/scripts/

IMPORTANT: Do NOT search the project directory for skill files. </accessing_skill_files>

<essential_principles> Skills are prompts. All prompting best practices apply. Be clear, be direct, assume Claude is smart.

Pure XML Structure: No markdown headings (#) in skill body. Use semantic XML tags:

• <objective> - What the skill does
• <quick_start> - Immediate actionable guidance
• <success_criteria> - How to know it worked

Progressive Disclosure: SKILL.md under 500 lines. Details go in references/ and workflows/.

Router Pattern (for complex skills):

Copyskill-name/
├── SKILL.md              # Router + essential principles
├── workflows/            # Step-by-step procedures (FOLLOW)
├── references/           # Domain knowledge (READ)
├── templates/            # Output structures (COPY + FILL)
└── scripts/              # Executable code (RUN)

Skill Types: Match structure to purpose:

Domain Discovery: Research the domain BEFORE asking users. Users want expertise IN the skill. </essential_principles>

1. Create a new skill
2. Audit or improve an existing skill
3. Add a component (workflow, reference, template, script)
4. Understand skill patterns

Wait for response before proceeding.

Intent-based routing (if user provides clear context):

• "verify content is current" → workflows/verify-skill.md
• "audit this skill" → workflows/audit-skill.md
• "create skill for X" → workflows/create-new-skill.md

After reading the workflow, follow it exactly.

<quick_reference> YAML Frontmatter (required):

Copy---
name: skill-name # lowercase-with-hyphens, ≤64 chars
description: | # What + When, ≤1024 chars, third person
  What this skill does.
  Use when users ask to <triggers>.
---

Simple Skill Structure:

Copy<objective>What the skill does</objective>
<quick_start>Minimal working example</quick_start>
<workflow>Step-by-step procedure</workflow>
<success_criteria>How to know it worked</success_criteria>

Router Skill Structure:

Copy<essential_principles>Always applies</essential_principles>
<intake>Question to ask user</intake>
<routing>Maps answers to workflows</routing>
<reference_index>Available references</reference_index>
<workflows_index>Available workflows</workflows_index>

Naming Convention: Prefer gerund form (verb + -ing):

• creating-skills, processing-pdfs, reviewing-code

</quick_reference>

<reference_index> All in references/:

<workflows_index> All in workflows/:

<templates_index> All in templates/:

<scripts_index> All in scripts/:

<success_criteria> A well-structured skill:

• Has valid YAML frontmatter (name + description)
• Uses pure XML structure (no markdown headings in body)
• Has essential principles inline in SKILL.md (if router pattern)
• Routes to appropriate workflows based on user intent
• Keeps SKILL.md under 500 lines
• Has been tested with real usage

</success_criteria>