skill-creator

# Skill Creator

Writing skills IS Test-Driven Development applied to process documentation.

Skills are reusable reference guides that teach Claude how to perform specific tasks. This skill helps you create or edit skills using a test-driven approach.

## The Iron Law

**No skill deploys without a failing test first.** This applies to both new skills and edits to existing skills.

If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.

## Instructions

Follow the RED-GREEN-REFACTOR cycle when creating or editing skills:

### RED: Run Baseline Tests Without the Skill

Before writing or editing ANY skill:

1. **Identify test scenarios**: What specific tasks should this skill help with?
2. **Run baseline tests**: Test Claude WITHOUT the skill (or with the old version)
3. **Document failures**: Record exactly how Claude fails, what it misses, or what it does wrong
4. **Capture natural behavior**: Note rationalizations, workarounds, or shortcuts Claude attempts

Ask yourself:
- What specific errors or mistakes happen without this skill?
- What does Claude try to do instead?
- What shortcuts does Claude rationalize?
- What edge cases does Claude miss?

**This is not optional.** If you skip baseline testing, you're guessing what to teach.

### GREEN: Write Minimal Skill Addressing Failures

Now write (or edit) the skill to address the specific failures you observed:

#### 1. Gather Requirements

For NEW skills, ask about:
- **Skill name**: What should the skill be called?
  - Must use lowercase letters, numbers, and hyphens only
  - Maximum 64 characters
  - Example: `pdf-processor`, `commit-helper`, `code-reviewer`

- **Location**: Where should the skill be created?
  - Personal skill: `~/.claude/skills/skill-name/`
  - Project skill: `.claude/skills/skill-name/`
  - Plugin skill: `plugin-name/skills/skill-name/`

For EDITING existing skills:
- What specific failures did baseline testing reveal?
- What new scenarios need