Meta Skill Creator

Based on answers, determine all frontmatter fields. For the full field reference, read references/frontmatter-fields.md.

Step 3: Plan and Confirm

Present the plan to the user before creating anything:

Plan for skill "{SKILL_NAME}":

Frontmatter:
  name: {SKILL_NAME}
  description: {DESCRIPTION} (X chars)
  disable-model-invocation: {true/false}
  allowed-tools: {list}
  {other fields if applicable}

Directories: {list only what's needed}
IMPROVEMENTS.md: included

Proceed? [y/n]

Wait for confirmation before continuing.

Step 4: Create the Skill

4a. Directory structure

Create only directories that will contain files:

mkdir -p ~/.claude/skills/{SKILL_NAME}
# Only create subdirectories if they'll have content:
# mkdir -p ~/.claude/skills/{SKILL_NAME}/references
# mkdir -p ~/.claude/skills/{SKILL_NAME}/scripts
# mkdir -p ~/.claude/skills/{SKILL_NAME}/examples

4b. Write SKILL.md

Generate the SKILL.md with:

• YAML frontmatter with all determined fields
• Markdown body in imperative form
• Under 500 lines total
• References to supporting files if they exist
• Self-Improvement Protocol section at the end (see below)

Follow the body writing rules from references/spec.md. Choose the appropriate skill pattern from references/patterns.md.

Always include this section at the end of the body:

## Self-Improvement Protocol
When you notice something that would improve this skill:
1. Append the insight to IMPROVEMENTS.md with date and context
2. Do NOT modify SKILL.md directly
3. Tell the user: "I logged a potential improvement for {SKILL_NAME}"

4c. Write IMPROVEMENTS.md

# Improvements Log for {SKILL_NAME}

Claude logs observations and improvement ideas here.
DO NOT modify SKILL.md directly. The user reviews and promotes changes.

## Format

- **Date**: YYYY-MM-DD
- **Context**: What was happening when the insight occurred
- **Observation**: What could be improved
- **Suggested change**: Concrete proposal

---

<!-- Entries below this line -->

4d. Supporting files (optional)

Only create if the skill needs them:

• references/ — for detailed specs, API docs, field references
• scripts/ — for executable automation (make executable with chmod +x)
• examples/ — for sample inputs/outputs

Step 5: Validate

Run the validation script against the new skill:

~/.claude/skills/meta-skill-creator/scripts/validate_skill.sh ~/.claude/skills/{SKILL_NAME}

Review the checklist from references/checklist.md.

If validation fails, fix issues and re-validate.

Step 6: Summary

Show the created structure:

find ~/.claude/skills/{SKILL_NAME} -type f

Tell the user:

• How to test: /skill-name [arguments]
• How evolution works: "Claude will log improvement ideas to IMPROVEMENTS.md. Review and promote changes when ready."

Self-Improvement Protocol

When you notice something that would improve this skill:

1. Append the insight to IMPROVEMENTS.md with date and context
2. Do NOT modify SKILL.md directly
3. Tell the user: "I logged a potential improvement for meta-skill-creator"