Skip to content
MCP Shelf

Skill Creator skill for Claude

Reviewed by Sophie Filer · Updated 27 Oct 2026

A skill for making skills: drafts one with you, tests it, and tunes when it switches on.

Most home-made skills fail in one of two quiet ways: Claude never loads them, or it loads them and still does the job badly. Skill Creator is built to catch both.

It interviews you about what the skill should do, writes a first draft, then runs a handful of test prompts with and without the skill so you can compare the results side by side. After that it can tune the description, the short line Claude uses to decide whether a skill is relevant.

When Claude reaches for it

  • Turning a workflow you repeat into a reusable skill
  • Improving a skill that exists but gives uneven results
  • Finding out why a skill does not switch on when it should

What is in the pod

  • A guided loop: capture intent, draft, test, review, revise
  • A simple format for test prompts and the checks each answer should pass
  • A small viewer that lays test results out for you to review
  • Scripts to tune the trigger description and to package the finished skill

Planting it

Claude Code

  1. Add the Anthropic skills marketplace once.
  2. Install the example-skills plugin, which includes skill-creator.
  3. Start a new session. Claude loads the skill on its own when a task matches.
Claude Code
/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills

Claude apps (web, desktop, mobile)

  1. On a paid plan, open Settings and find the Skills section.
  2. Switch on skill-creator from Anthropic's examples, or upload the folder as a zip.

By hand (Claude Code)

  1. Download the skill folder from GitHub.
  2. Put it in ~/.claude/skills/ for every project, or .claude/skills/ inside one project.
By hand (Claude Code)
~/.claude/skills/skill-creator/SKILL.md

What it needs

  • Claude Code for the full test loop (some scripts call the claude command line tool)
  • Python 3 for the helper scripts

Notes from the pea patch

  • Write three or four test prompts that sound like you on a busy day, not tidy textbook requests. Those are the ones that reveal a weak description.
  • You can skip the formal testing for a skill that is mostly about taste, such as a writing style. It earns its keep on skills with a right answer.

Pea-fect partners on the shelf

Basic MemoryA good place to keep notes on what each skill version changed and why.GitHubShare the finished skill folder as a repo others can install from.