skill-kit
Skill1 starsChanged 9 days agoMITView on GitHub
Creates, lints and rewrites skills to one compact standard, and proves that a rewrite keeps every rule. Use when writing or changing any skill in this repo, or as /skill-kit new, lint or rewrite. Not for plugin manifests or hooks (use plugin-authoring).
3 other projects use a version of this.
Adopted by
Most recently taken up by
- monkeychen/skillstheir own version, first seen Oct 20, 2026
- es6kr/skillstheir own version, first seen Oct 13, 2026
- sezeryavuz/skillstheir own version, first seen Jun 30, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- sezeryavuz/skills★ 7same name
- es6kr/skills★ 2same name
- monkeychen/skills★ 1same name
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 repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- installer/CLAUDE.mdCLAUDE.md
- site/CLAUDE.mdCLAUDE.md
- plugin-authoringSkill
- releaseSkill
- stackgen-pluginSkill
- vwf-pluginSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 78
Never rewrite with no ledger.
- Distinctive: line 80
Never change behavior in a rewrite.
- Very specific: line 82
Never copy a rule that p:plugins:check owns.
- Distinctive: line 84
Never bump a version in a rewrite.
- Distinctive: line 86
Never commit, merge or push without consent.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
skill-kit
Holds the standard for every skill in this repo. Scripts decide exact rules, and
a fresh reviewer decides judgment rules. In all commands, <skill-kit> is the
folder of this skill.
Invoke
| Form | Workflow | Loads |
new <archetype> <name> | new.md | sometimes |
lint [path | --all] | lint.md | sometimes |
rewrite <path> | rewrite.md | sometimes |
Routing
| Doing | Read | Loads |
| Writing any part of a skill | standard.md | always |
| Writing prose | style.md | always |
| Choosing an archetype | archetypes.md | sometimes |
| Reading a lint finding | rules.md | sometimes |
| Moving this skill into a plugin | move-to-plugin.md | sometimes |
State
| File | Access | Owner |
| The target skill folder | read/write | this skill, by consent |
| The scratch copy of the old skill | read/write | this skill |
| The scratch ledger of a rewrite | read/write | this skill |
assets/config.json | read | this repo |
assets/archetypes.json | read | this skill |
Phases
| Phase | Gate | File |
| Choose archetype | user, only if two fit | new.md |
| Scaffold | auto | new.md |
| Lint | auto | lint.md |
| Ledger | auto | rewrite.md |
| Drop a rule | user | rewrite.md |
Halt and pause
| ID | Condition | Action |
| H1 | The target folder exists at new | Stop, and name the folder |
| H2 | A lint error remains | Fix it, then run lint again |
| H3 | A ledger entry has no match after two rounds | Stop, and show the entries |
| H4 | The rewrite wants to drop a rule | Ask the user for each entry |
Output
new: a skill folder with TODO markers, and the lint result.lint: one line per finding, and a count per rule.rewrite: the rewritten skill, the settled ledger, and word counts before and after.
Never
- Never rewrite with no ledger; extract one first — a lost rule fails silently at run time.
- Never change behavior in a rewrite; make a separate change — each needs its own review.
- Never copy a rule that
p:plugins:checkowns; link to it — two owners drift apart. - Never bump a version in a rewrite; record the release level — a version moves only at release.
- Never commit, merge or push without consent; ask first — the user owns each landing.
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.