create-skill
/create-skill
Scaffold a new Claude Code skill — create the skill directory and a well-formed SKILL.md (frontmatter + instructions). Use when the user wants to "create/new/scaffold a skill", "写个 skill", or "把这个流程做成 skill". First arg "global" saves to ~/.claude/skills, otherwise project ./.claude/skills.
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 03.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Scaffold a new Claude Code skill — create the skill directory and a well-formed SKILL.md (frontmatter + instructions). Use when the user wants to "create/new/scaffold a skill", "写个 skill", or "把这个流程做成 skill". First arg "global" saves to ~/.claude/skills, otherwise project ./.claude/skills.
Triggers from the description
Arguments
/create-skill [global] [skill description...]
Original author description
Scaffold a new Claude Code skill — create the skill directory and a well-formed SKILL.md (frontmatter + instructions). Use when the user wants to "create/new/scaffold a skill", "写个 skill", or "把这个流程做成 skill". First arg "global" saves to ~/.claude/skills, otherwise project ./.claude/skills.
How it works
- Instructions
- Important
- Arguments
SKILL.md preview
---
name: create-skill
description: Scaffold a new Claude Code skill — create the skill directory and a well-formed SKILL.md (frontmatter + instructions). Use when the user wants to "create/new/scaffold a skill", "写个 skill", or "把这个流程做成 skill". First arg "global" saves to ~/.claude/skills, otherwise project ./.claude/skills.
disable-model-invocation: true
argument-hint: '[global] [skill description...]'
---
Create a new skill for the user.
## Instructions
1. **Determine save location**: Check the first argument token(s).
- `global` → save to `~/.claude/skills/<skill-name>/SKILL.md`, and treat the remaining tokens as the skill description.
- A destination naming the cc-skills repo (e.g. `to ~/Projects/cc-skills`) → save to `~/Projects/cc-skills/.claude/skills/<skill-name>/` (skills live under `.claude/skills/`, NOT the repo root). Follow that repo's `CLAUDE.md`: gen-image is the reference template, no secrets in committed files (public repo), and finish with its "Adding a skill" checklist (`.sync-targets.json` + `bun run sync` + `bun run readme`).
- Otherwise, save to `./.claude/skills/<skill-name>/SKILL.md` (project scope), and treat all tokens as the skill description.
The **command name comes from the directory name** (`my-skill/` → `/my-skill`), not from the `name` field.
2. **Decide the skill type** — this drives the frontmatter:
- **Reference skill** (conventions, domain knowledge, style guides): loaded inline alongside the conversation. Leave it model-invocable.
- **Task skill** (deploy, commit, codegen, multi-step actions): add `disable-model-invocation: true` so it only runs as `/name` and Claude never fires it on its own — especially for anything with side effects.
3. **Gather information** (use arguments if provided, otherwise ask):
- Skill name (directory name → the command)
- Description (most important — see the rule below)
- Body / instructions
- Any optional frontmatter the skill actually needs (see reference.md)
**description is the field that decides auto-loading.** Pack in (a) what it does, (b) when to use it, (c) the trigger words a user would naturally type — lead with the top use case. `description` + `when_to_use` are merged and **truncated to 1536 chars** in the skill listing, so front-load the essentials. If there are many trigger phrases, split them into a `when_to_use` field.
4. **Create the skill directory and SKILL.md.** Only `description` is recommended; every other field is optional (`name` defaults to the directory name). Minimal frontmatter:
```yaml
---
name: <skill-name> # display name only; usually = directory name
description: <what it does + when to use + the words a user would actually say>
# disable-model-invocation: true # task skills / side effects — run only as /command
# argument-hint: '<args>' # autocomplete hint if it takes arguments
# allowed-tools: Bash(git commit *) ... # pre-approve only the tools it needs
# paths: ["**/*.ts"] # auto-activate only when matching files are touched
# user-invocable: false # hide from / menu for pure background knowledge
---
```
For the full field set (`when_to_use`, `arguments`, `disallowed-tools`, `model`, `effort`, `context`/`agent`, `hooks`, `shell`), string-substitution variables, dynamic context injection, and the companion-file pattern, see [reference.md](reference.md).
5. **Keep the body lean.** Say WHAT to do, not why. Once loaded, the rendered SKILL.md stays resident across turns, so write standing instructions, not one-shot steps. Keep it under ~500 lines; move big reference/examples/long scripts into companion files and load them on demand. Reference scripts via `${CLAUDE_SKILL_DIR}/foo.sh`, never a hardcoded `.claude/skills` path.
6. **After creating, suggest a test**: try the natural phrasing (auto-trigger) and the direct `/skill-name` (manual) — confirm it both fires and does the right thing.
## Important
Propose the complete SKILL.md draft and the exact save path first. Create the directory and write the files only after the user confirms. If the skill's intent, name, or scope is unclear, ask before drafting.
## Arguments
$ARGUMENTS
Files in this package (2)
- SKILL.md 4 KB
- reference.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · sorrycc/skills | 100 | MIT |
| mgiovani/cc-arsenal | 100 | MIT |
| zylos-ai/zylos-core | 100 | MIT |
| mthines/agent-skills | 100 | MIT |
| jongio/skills | 100 | MIT |
| fairladyz625/harness-anything | 100 | AGPL-3.0 |
| coco-research/coco | 100 | MIT |
| builderio/agent-native | 100 | MIT |
| BrandeisPatrick/silo-harness | 100 | MIT |
Database snapshot: 13.11.2026 · package version e90124d23a36 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95skill-creator
Guide for creating NEW skills from scratch. This skill should be used when users want to create a new skill or scaffold a skill directory. Triggers on "create a skill", "new skill", or "scaffold skill". Do NOT use for updating existing skills - use claude-code-expert instead. - 100skill-writer
Guide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure. - 90Project Scaffolding
This skill should be used when the user wants to set up Claude for a project, create a CLAUDE.md file, scaffold the .claude directory, initialize an AI workflow, configure a project for Claude, set up dev intelligence, initialize a new project, or do a new project setup.… - 98agent-skill-builder
Quickly creates new Claude Code skills or translates ChatGPT projects into Claude Code skills. Handles skill scaffolding, frontmatter, directory structure, and ChatGPT-to-Claude migration. Use when the user wants to 'create a skill,' 'make a new slash command,' 'convert a… - 100new-skill
Scaffold a new skill that follows this repo's conventions — interviews for purpose, trigger phrases, and tool needs, then writes `.claude/skills/<name>/SKILL.md` from the skill template with frontmatter and body that pass the integrity gates on first try. Use when user says… - 95creating-agent-skills
Create and refine Claude Code Skills. Use when authoring SKILL.md files, building new skills, or improving existing skill structure and best practices.