create-skill
Skill0 starsChanged 9 months agoMITView on GitHub
Create a new Claude Code skill from a description. Use when the user asks to create, build, or make a skill, command, or capability for Claude Code.
- Reads credentials
- Installs packages
148 other projects use a version of this.
Adopted by
Most recently taken up by
- BrandeisPatrick/silo-harnesstheir own version, first seen Nov 16, 2026
- sphnx-io/Claude-Skillstheir own version, first seen Nov 16, 2026
- jasoncg8/claude-skillstheir own version, first seen Nov 16, 2026
- neomjs/neo-agent-skillstheir own version, first seen Nov 15, 2026
- shishtpal/SpiAgentHarnesstheir own version, first seen Nov 15, 2026
- shoodoow/kurutheir own version, first seen Nov 15, 2026
Used with
Projects with it also use review-bugbot, migrate-to-skills 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.
0mlkrizzz655335vSkillreview-bugbot
缺陷导向代码审查。用 Bugbot 子代理找 bug。
Also in 5 projects that use this
32103210Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.
Also in 8 projects that use this
32103210Skillupdate-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Also in 8 projects that use this
PandelisZSkillupdate-cli-config
View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.
Also in 7 projects that use this
yawningwhaleAISkillbuild-premium-website
Build a premium, animated marketing website (React + Vite + Tailwind + GSAP) for any industry. Use when the user asks to "build a website", "make a landing page for [business]", "build a marketing site", or wants a high-end animated company website. Adapts color, copy, services, and signature animation to the industry.
Also in 6 projects that use this
yawningwhaleAISkillinstantly-campaign
Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.
Also in 5 projects that use this
- +1 more from 32103210
Other versions148 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 148
- microsoft/vscode★ 195ksame name
- CherryHQ/cherry-studio★ 54ksame name
- videojs/video.js★ 40ksame name
- BuilderIO/agent-native★ 7.7ksame name
- stagewise-io/stagewise★ 6.8ksame name
- dotnet/skills★ 6.2ksame name
- xstongxue/best-skills★ 2.9ksame name
- Lilac-Labs/gini-agent★ 1.9ksame name
- Open-Curiosity/gini-agent★ 1.9ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
138 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 repository4 other files it gives its agents.
- generate-imageSkill
- reconSkill
- send-emailSkill
- spriteSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 15 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 138 edited versions we read keep these.
15
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 9
Create Claude Code skills that follow established patterns and best practices.
- Distinctive: line 17
When should it trigger? (description keywords)
- Distinctive: line 21
If the user's request is clear enough, skip unnecessary questions.
- Distinctive: line 25
If the skill involves external APIs, libraries, or unfamiliar domains:
- Distinctive: line 26
Use WebSearch to find current documentation and approaches
- Distinctive: line 28
Look for Python stdlib solutions before adding dependencies
- Distinctive: line 39
When to use it
- Distinctive: line 43
Default (both user and model) for reference/utility skills
- Distinctive: line 46
Only grant what's necessary
- Very specific: line 47
Use patterns like Bash(python3 ~/.claude/skills/SKILL_NAME/scripts/*.py *)
- Distinctive: line 50
Use scripts for: API calls, file manipulation, deterministic operations
- Distinctive: line 51
Use instructions for: decision-making, interpretation, flexible workflows
- Very specific: line 55
Create the skill at ~/.claude/skills/{skill-name}/:
- Distinctive: line 99
No pip install required
- Very specific: line 105
Keep SKILL.md lean, put details in references
- Distinctive: line 109
After creating the skill:
- Distinctive: line 110
Verify the skill appears in available skills
- Distinctive: line 111
Test invocation with a simple case
“Common” is measured: kept by at least 6 in 10 of the 138 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
Create Claude Code skills that follow established patterns and best practices.
Process
1. Clarify Requirements
Ask the user:
- What should the skill do? (core functionality)
- When should it trigger? (description keywords)
- What inputs does it need? (arguments, files, environment variables)
- What outputs does it produce? (files, terminal output, side effects)
If the user's request is clear enough, skip unnecessary questions.
2. Research (if needed)
If the skill involves external APIs, libraries, or unfamiliar domains:
- Use WebSearch to find current documentation and approaches
- Favor recent sources (last 2-3 months)
- Look for Python stdlib solutions before adding dependencies
3. Design the Skill
Determine the skill structure:
Name: lowercase, hyphenated (e.g., generate-report, sync-notes)
Description: The trigger mechanism. Include:
- What the skill does
- Keywords that should activate it
- When to use it
Invocation mode:
disable-model-invocation: truefor skills with side effects (sending, deploying, deleting)- Default (both user and model) for reference/utility skills
Tools needed (allowed-tools):
- Only grant what's necessary
- Use patterns like
Bash(python3 ~/.claude/skills/SKILL_NAME/scripts/*.py *)
Script vs instructions:
- Use scripts for: API calls, file manipulation, deterministic operations
- Use instructions for: decision-making, interpretation, flexible workflows
4. Create Files
Create the skill at ~/.claude/skills/{skill-name}/:
SKILL.md (required):
---
name: skill-name
description: Clear description including trigger keywords and when to use.
argument-hint: [arg1] [--flag value]
allowed-tools: Bash(python3 ~/.claude/skills/skill-name/scripts/*.py *)
disable-model-invocation: true # if has side effects
---
# Skill Title
Brief overview of what this skill does.
## Usage
How to use the skill with example commands.
## Options
| Flag | Description | Default |
|------|-------------|---------|
| `--flag` | What it does | Default value |
## Examples
Concrete examples showing common use cases.
## Interpreting user requests
How to translate natural language into skill invocations:
1. Extract key information from the request
2. Map to appropriate flags/arguments
3. Handle edge cases
## Environment setup
Any required environment variables or configuration.scripts/ (if needed):
- Python scripts using only stdlib when possible
- No pip install required
- Load API keys from environment or .env files
- Clear error messages with setup instructions
references/ (if needed):
- Additional documentation Claude should reference
- Keep SKILL.md lean, put details in references
5. Test the Skill
After creating the skill:
- Verify the skill appears in available skills
- Test invocation with a simple case
- Confirm outputs match expectations
Reference
See skill-patterns.md for:
- Frontmatter field reference
- Established patterns from existing skills
- Best practices from official docs
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.

