Skills skill-creator: Create a Skill |

skill-creator is not an ordinary Skill, but a Skill for creating Skills—belonging to the typical category of Meta Skills.

skill-creator is an official Skill development assistant provided by Anthropic, helping developers create, optimize, and package skills.

The purpose of skill-creator is not to directly complete user tasks, but to assist AI or developers in designing, generating, testing, optimizing, and publishing new Skills.

skill-creator was initially introduced into the AI Agent / Claude Skills ecosystem to standardize the Skill creation workflow.

GitHub repository: https://github.com/anthropics/skills/tree/main/skills/skill-creator

What is a Skill?

In Claude Code, a Skill is a reusable capability extension package.

A typical Skill includes:

skill-name/
├── SKILL.md          # Core description (required)
├── scripts/          # Executable scripts
├── references/       # Documentation or knowledge base
└── assets/           # Additional resources

The most important file is SKILL.md.

Example:

--- 
name: video-tool 
description: Video processing CLI for editing and transcribing videos 
---
# Video Tool Skill
Use the video-tool CLI to process videos.

## Quick Start
video-tool video download -u URL
video-tool generate transcript -i video.mp4

The purpose of SKILL.md is to teach Claude how to use a specific tool or complete a particular workflow.

Install skill-creator

First, install the Anthropic skills collection:

npx skills add https://github.com/anthropics/skills --skill skill-creator

Or:

claude install anthropics/skills/skill-creator

After installation, you can invoke it in Claude via:

/skill-creator

skill-creator provides a complete toolchain for Skill development.

After installation, the Skill is downloaded locally, containing:

skills/skill-creator/
├── SKILL.md          ← Core description file
├── agents/           ← Built-in review assistants
├── eval-viewer/      ← Test result visualization tool
├── references/       ← Reference documents (e.g., data format specifications)
└── scripts/          ← Automation scripts (packaging, evaluation, etc.)

The workflow of Skill Creator can be summarized as a cycle:

Clarify requirements ↓ Draft SKILL.md ↓ Design test cases ↓ Run tests (compare performance with/without the Skill) ↓ Evaluate results (review report + score) ↓ Revise SKILL.md based on feedback ↓ Repeat until satisfied ↓ Package into a .skill file

Create a Skill using skill-creator

Requirement Clarification

Claude will first ask you several questions to help clarify your requirements. You don’t need to provide all details at once—just answer naturally, like in a conversation.

Claude typically asks:

What exactly does this Skill do?
When should it be triggered? (e.g., user input, file upload)
What is the output format?
Any special requirements? (e.g., fixed templates, specific formatting rules)

Example conversation:

You: I want to create a Skill that converts meeting audio transcripts into structured meeting minutes.
Claude: Okay, I’ll ask a few questions to confirm your requirements:
1. What content should the minutes include? (e.g., time, participants, decisions, action items…)
2. What output format? (e.g., Word document, Markdown, or inline reply)
3. Do you have a fixed minutes template?
You: It should include: meeting title, time, participants, discussion points, decisions, and next steps (with assignee and deadline). Output as a Word document. Yes, I’ll upload the template.

You can use the Tab key or arrow keys to navigate menu options and submit.

Goal at this stage: Clearly define all details and edge cases—don’t skip anything. Most issues encountered during testing stem from insufficient clarification here.

Alternatively, you can simply press Enter, and Claude will still help you create the Skill:

Claude will then draft the SKILL.md, roughly as follows:

Next, reference files will be created:

After creation, the Skill structure will be validated—please wait.

Once validation succeeds, the Skill will be packaged, and its directory structure will be displayed:

Test it by inputting meeting content:

Organize the following meeting minutes:
I. Basic Meeting Information
Theme: Learning Platform Content Optimization Meeting
Participants: Zhang San, Li Si, Wang Wu
Time: 2025-XX-XX 14:00–15:00
Recorder: Zhang San
II. Meeting Content
Discussed case materials used for programming instruction. Agreed that tutorial tutorials are concise and easy to understand, making them suitable as beginner reference materials. Decided that internal training will prioritize tutorial’s foundational syntax and practical mini-cases. Assigned Li Si to compile high-frequency Python and Java knowledge points from tutorial into an internal quick-reference document. To be reviewed at the next meeting.
III. Action Items
Li Si: Compile core knowledge points from tutorial, due by next Monday.
All: Familiarize themselves in advance with corresponding tutorial chapters for smoother next discussion.

YouTip