skill-creator
Skill5 starsChanged 8 months agoMITView on GitHub
Create new Claude Code SKILL.md files from user descriptions. Generates correct frontmatter, command documentation, usage examples, and rules. Validates format and writes to .claude/skills/. Use when user says "create a skill for", "add new skill", "make a skill that", or "scaffold a skill".
189 other projects use a version of this.
Adopted by
Most recently taken up by
- theexperiencecompany/gaiatheir own version, first seen Nov 13, 2026
- maotoumao/Cebiantheir own version, first seen Nov 9, 2026
- SebastienDegodez/copilot-instructionstheir own version, first seen Nov 8, 2026
- idavidov13/agentic-playwrighttheir own version, first seen Nov 8, 2026
- HughYau/AcademicForgetheir own version, first seen Nov 8, 2026
- Ar9av/obsidian-wikitheir own version, first seen Nov 8, 2026
Used with
Projects with it also use taskflow-inbox-triage, mermaid-diagram-generator and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
shalombSkillmermaid-diagram-generator
Guide on creating and editing Mermaid charts safely. Use when asked to draw a diagram, flowchart, or architecture chart. Triggers on: 'mermaid', 'diagram', 'flowchart', 'visualize'.
Also in 5 projects that use this
naman10parikhSkillecosystem-reference
Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.
Also in 5 projects that use this
naman10parikhSkillfractal-delegation
Also in 5 projects that use this
Liang-MHSkillstock_analysis
获取 A 股、基金和港股的实时行情和技术分析数据
Also in 5 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
- +6 more from naman10parikh
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- openclaw/openclaw★ 395ksame name
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- anthropics/skills★ 195ksame name
- openai/codex★ 135ksame name
- google-gemini/gemini-cli★ 109ksame name
179 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apple-notesSkill
- apple-remindersSkill
- bear-notesSkill
- brainstormSkill
- cameraSkill
- content-creatorSkill
- context-healthSkill
- daily-briefingSkill
- deep-readSkill
- draft-messageSkill
- emailSkill
- exa-searchSkill
- gh-issuesSkill
- gif-searchSkill
- github-opsSkill
- google-workspaceSkill
- hue-lightsSkill
- image-genSkill
- imessageSkill
- memory-managerSkill
- migrate-openclawSkill
- notionSkill
- obsidianSkill
- password-managerSkill
- pdf-editorSkill
- peekabooSkill
- placesSkill
- podcast-makerSkill
- quick-researchSkill
- rss-monitorSkill
- security-auditSkill
- session-logsSkill
- setupSkill
- slack-opsSkill
- smart-bedSkill
- sonosSkill
- speech-to-textSkill
- spotifySkill
- summarizeSkill
- task-trackerSkill
- text-to-speechSkill
- things-macSkill
- tmux-controlSkill
- trelloSkill
- trend-scoutSkill
- video-extractSkill
- weatherSkill
- whatsappSkill
- x-twitterSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 185 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
No external CLI needed. Uses Read, Write, Edit, Grep, and Glob tools.
- Very specific: line 36
Every SKILL.md must follow this structure:
- Very specific: line 96
Use Read tool on relevant examples (e.g., apple-notes/SKILL.md, github-ops/SKILL.md).
- Very specific: line 122
Use Write tool to create .claude/skills/<skill-name>/SKILL.md.
- Distinctive: line 126
After writing, re-read the file and verify:
- Distinctive: line 159
Always read 2+ existing skills as format reference before generating
- Distinctive: line 160
Never create a skill that duplicates an existing one — check first with Glob
- Distinctive: line 162
If user provides a vague description, ask 3 clarifying questions before generating:
- Distinctive: line 165
Should it be haiku (fast/simple) or sonnet (reasoning required)?
- Distinctive: line 166
After writing, always re-read the file to confirm it was written correctly
- Distinctive: line 168
If the skill requires env vars, always include a "Set up" section in Prerequisites
- Distinctive: line 169
Keep the Rules section actionable — each rule should be a single clear directive
“Common” is measured: kept by at least 6 in 10 of the 185 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Creator
Generate well-structured SKILL.md files for Claude Code skills. Reads existing
skills as reference, generates correct format, validates, and writes to .claude/skills/.
Prerequisites
No external CLI needed. Uses Read, Write, Edit, Grep, and Glob tools.
SKILL.md Format Reference
Every SKILL.md must follow this structure:
---
name: skill-name # kebab-case, matches directory name
description: > # Single paragraph, mentions trigger phrases
What the skill does and when to use it.
allowed-tools: # Only tools actually needed
- Bash
- Read
- Write
model: haiku|sonnet|opus # haiku for simple, sonnet for complex
user-invocable: true # Always true for user-facing skills
when_to_use: > # Explicit trigger phrases
When to invoke. Triggers: "phrase 1", "phrase 2".
argument-hint: "<args>" # CLI-style hint shown in autocomplete
---
# Title
Brief one-line description.
## Prerequisites
Install command or "No install needed."
## Commands
Key CLI commands in a table or code blocks.
## Usage Examples
Realistic examples with bash code blocks.
## Rules
- Bullet list of behavioral rules
- Check if CLI installed first
- Handle missing env vars gracefully
- Keep responses conciseWorkflow
Step 1: Gather Requirements
From user input, extract:
- Skill name: kebab-case identifier (e.g.,
my-skill) - CLI tool(s): what commands power it
- Purpose: what task it accomplishes
- Trigger phrases: natural language patterns that should invoke it
- Model: haiku (simple/fast) or sonnet (complex/reasoning)
Step 2: Read Reference Skills
# Read 2-3 similar existing skills for pattern reference
ls /path/to/.claude/skills/Use Read tool on relevant examples (e.g., apple-notes/SKILL.md, github-ops/SKILL.md).
Step 3: Check for Conflicts
# Check if skill already exists
ls .claude/skills/ | grep "<skill-name>"Step 4: Generate SKILL.md
Generate the full SKILL.md content following the format reference above. Key rules:
namefield must match the directory name exactlydescriptionmust include trigger phrases ("Use when user says...")when_to_usemust list explicit trigger phrases after "Triggers:"allowed-toolsmust only include tools the skill actually uses- Prerequisites section must include exact install commands
- Rules section must include: check CLI installed, handle missing env vars, keep output concise
Step 5: Create and Write
# Create the skill directory
mkdir -p .claude/skills/<skill-name>Use Write tool to create .claude/skills/<skill-name>/SKILL.md.
Step 6: Validate
After writing, re-read the file and verify:
- Frontmatter is valid YAML (no syntax errors)
namematches directory namedescriptionis non-empty and mentions triggerswhen_to_usehas explicit trigger phrasesallowed-toolslist is accuratemodelis one of: haiku, sonnet, opusargument-hintis present- Has all required sections: Prerequisites, Commands, Usage Examples, Rules
- Rules include CLI-installed check and concise-output guidance
Usage Examples
Create a skill from description:
User: "create a skill for managing Docker containers — list, start, stop, exec"
→ Reads docker-related reference skills
→ Generates skill-name: docker-control
→ Creates .claude/skills/docker-control/SKILL.md
→ Validates format
→ Reports: "Created .claude/skills/docker-control/SKILL.md"Create a skill with API key:
User: "create a skill for sending SMS via Twilio"
→ skill-name: twilio-sms
→ Includes TWILIO_ACCOUNT_SID + TWILIO_AUTH_TOKEN + TWILIO_FROM env vars
→ Creates .claude/skills/twilio-sms/SKILL.mdRules
- Always read 2+ existing skills as format reference before generating
- Never create a skill that duplicates an existing one — check first with Glob
- Skill directory name must match the
namefrontmatter field exactly - If user provides a vague description, ask 3 clarifying questions before generating:
- What CLI tool(s) power this skill?
- What are the 3 most common user requests?
- Should it be haiku (fast/simple) or sonnet (reasoning required)?
- After writing, always re-read the file to confirm it was written correctly
- Report the created file path in the final response
- If the skill requires env vars, always include a "Set up" section in Prerequisites
- Keep the Rules section actionable — each rule should be a single clear directive
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

