references
Skill1 starsChanged yesterdayMITView on GitHub
How to create a plugin skill's SKILL.md from .claude/templates/skill-template.md. plugins/<plugin>/skills/<skill>/SKILL.md, plus any supporting files beside it (references/, scripts/, assets/). Read 2026-11-10, Claude Code docs skills: This repository:
12 other projects use a version of this.
Adopted by
Most recently taken up by
- uwonu606/claude-skillstheir own version, first seen Nov 16, 2026
- swarm-routing/skillstheir own version, first seen Nov 15, 2026
- LordVayron/video-factorytheir own version, first seen Nov 15, 2026
- jmche/skills-hubtheir own version, first seen Oct 20, 2026
- arthur-plautz/research-toolkittheir own version, first seen Oct 15, 2026
- darellchua2/civiltekk-opencode-claude-skillstheir own version, first seen Sep 18, 2026
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- alfredxw/denova★ 1ksame name
- LordVayron/video-factory★ 67same name
- openbkn-ai/bkn-sdk★ 27same name
- gohypergiant/agent-skills★ 25same name
- howells/fiction★ 23same name
- jeffsenso/dolibarr-skills★ 9same name
- v-open-platform/ai-app-skills★ 8same name
- darellchua2/civiltekk-opencode-claude-skills★ 7same name
- swarm-routing/skills★ 1same name
- arthur-plautz/research-toolkit★ 0same name
2 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 repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- docs-maintenanceSkill
- plugin-catalog-changesSkill
- plugin-iconsSkill
- plugin-releasesSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
When a plugin gains a skill, and when a skill's purpose or triggers change.
- Very specific: line 15
Read 2026-11-10, Claude Code docs skills:
- Very specific: line 34
Create plugins/<plugin>/skills/<skill>/ and copy the template to SKILL.md.
- Distinctive: line 36
Add only the optional fields the skill needs.
- Distinctive: line 37
Write the body; move long material to files beside it and link them.
- Distinctive: line 53
Never take another plugin's skill as a model.
- Distinctive: line 63
Never add a frontmatter field the skill does not use.
- Distinctive: line 64
Never put a secret or a machine path in a skill.
“Common” is measured: kept by at least 6 in 10 of the 9 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
How to create a plugin skill's SKILL.md from .claude/templates/skill-template.md.
Produces
plugins/<plugin>/skills/<skill>/SKILL.md, plus any supporting files beside it (references/, scripts/, assets/).
When
- When a plugin gains a skill, and when a skill's purpose or triggers change.
Sources
Read 2026-11-10, Claude Code docs skills:
- Frontmatter is read only when the opening
---is the file's first line; YAML that doesn't parse loads the skill with no fields set. nameis optional and defaults to the directory name;descriptionis recommended: "Put the key use case first: the combineddescriptionandwhen_to_usetext is truncated at 1,536 characters in the skill listing."- Optional fields:
when_to_use,argument-hint,arguments,disable-model-invocation,user-invocable,allowed-tools,disallowed-tools,model,effort,context,agent,background,hooks,paths,shell,metadata,license,compatibility. - Outside Claude Code (claude.ai uploads, the Skills API) only
name,description,license,compatibility,metadataandallowed-toolsare allowed; any other field fails the upload with a hard error. - "Keep
SKILL.mdunder 500 lines. Move detailed reference material to separate files."
Placeholders
| Value | Meaning | True value from |
{{skillName}} | Kebab-case name, identical to the directory | The skill's directory |
{{skillDescription}} | What the skill does and when to use it, key use case first | The skill's own files |
{{skillTitle}} | The H1 heading | The skill's purpose |
{{skillInstructions}} | The body Claude follows | The skill's procedure |
Procedure
- Create
plugins/<plugin>/skills/<skill>/and copy the template toSKILL.md; the---stays on line 1. - Fill
nameanddescription; delete the instruction comment. - Add only the optional fields the skill needs. For a plugin that reaches Claude, keep to the portable subset, or the skill fails to upload there.
- Write the body; move long material to files beside it and link them.
- Run the checks.
Rules
Official:
- Frontmatter on line 1, valid YAML.
descriptionpluswhen_to_usewithin 1,536 characters, key use case first.SKILL.mdunder 500 lines.
This repository:
- The description is written from the skill's own files, imperative, with no quoted trigger phrases.
- A colon goes only after a field name. No value holds a colon or is wrapped in quotes: reword the sentence instead, so every value stays plain text that strict YAML parsers read.
nameequals the directory name.- Never take another plugin's skill as a model.
Checks
claude plugin validate --strict plugins/<plugin>.claude plugin details plugins/<plugin>: the skill is listed, with its size.python3 scripts/validators/skill-names-consistency.pyandpython3 scripts/validators/skill-size.py.
Never
- Never add a frontmatter field the skill does not use.
- Never put a secret or a machine path in a skill.
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.

