skill-creator

name	skill-creator
description	Create a new Claude Code skill — research from web, write SKILL.md, register in plugin.json, add to README.md, create experience log. Trigger on /skill-creator, or when asked to create a new skill.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Edit, Browser

Skill Creator

Create a new Claude Code skill from scratch. Researches content from multiple web sources, synthesizes, writes, and validates.

Workflow

1. Define the skill

Gather from user or infer:

• Name — kebab-case, e.g. my-analyzer
• Description — one line, what triggers it
• Purpose — what problem does it solve?
• When to trigger — user intent, keywords, scenarios
• Allowed tools — Read, Grep, Glob, Bash, Edit, Browser, etc.
• Key steps — what should the agent do?

2. Research from web

Search multiple sources for the skill's topic:

• Web search — general techniques, best practices, common pitfalls
• Official docs — library/framework documentation, API references
• GitHub — examples, issues, real-world usage
• Blogs/tutorials — step-by-step guides, comparisons
• Stack Overflow — common problems and solutions

Minimum 3 sources. For each source note:

• What technique or approach does it suggest?
• What are the trade-offs or limitations?
• Is it up-to-date? (version, deprecation, alternatives)
• Does it apply to the user's context?

3. Synthesize and write SKILL.md

Compare findings across sources. Decide what to include based on:

• What sources agree on (most reliable)
• What fits the user's project context
• What is simplest yet effective

Then write the SKILL.md:

.claude/skills/<name>/
└── SKILL.md

Use template:

---
name: <name>
description: <description>
user-invocable: true
allowed-tools: Read, Grep, Glob, Bash
---

# <Title>

<2-3 sentence summary>

## When to use

- ...

## Workflow

### 1. ...
### 2. ...

## Output

- ...

## Experience Log

_This skill learns from experience. Mechanism:_

- **Read** `.claude/experience/<name>.md` at skill start.
- **Write** to `.claude/experience/<name>.md` after use.
- **Format**: `YYYY-MM-DD: <lesson>`
- **Evolve**: If same issue repeats 3+ times, update this SKILL.md.

4. Register in plugin.json

Add "./.claude/skills/<name>" to the skills array in .claude-plugin/plugin.json.

5. Add to README.md

Add entry in the appropriate category section (Engineering / Agent Workflow / Automation & Integration).

6. Create experience log

Create .claude/experience/<name>.md with initial content.

7. Test and verify

• SKILL.md has valid YAML frontmatter (starts and ends with ---)
• plugin.json has valid JSON
• README.md entry links to correct path
• Experience file exists
• Test the skill — invoke /skill-name or simulate the workflow to confirm it works in practice

Rules

• Do not overwrite existing skills — check if directory exists first.
• YAML frontmatter must have: name, description, user-invocable, allowed-tools.
• Keep the skill focused on one concern.
• Add Experience Log section to every skill.
• Update plugin.json and README.md alphabetically, not at the end.