skills
CLAUDE.md1 starsChanged 6 months agoMITView on GitHub
Skills are organized into bucket folders under skills/: Every skill in engineering/, productivity/, or misc/ must appear in the root README.md and have an entry in .claude-plugin/plugin.json. Skills in in-progress/ and deprecated/ must not appear in either. Each skill directory must contain a SKILL.md with name and description frontmatter. Each bucket folder has a README.md listing its skills with one-line descriptions, with each skill name linked to its SKILL.md. Additional reference files (e.g., setup.md, patterns.md) are placed alongside SKILL.md in…
In this repository4 other files it gives its agents.
- tanstack-formSkill
- hello-worldSkill
- ship-branch-giteaSkill
- ship-branchSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 11
Every skill in engineering/, productivity/, or misc/ must appear in the root README.md and have an entry in .claude-plugin/plugin.json.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Skills Repository
Skills are organized into bucket folders under skills/:
engineering/— code-related work (form patterns, testing, tooling)productivity/— workflow optimizationmisc/— rarely-used or demo skillsin-progress/— draft skills, not shareddeprecated/— obsolete skills, not shared
Every skill in engineering/, productivity/, or misc/ must appear in the root README.md and have an entry in .claude-plugin/plugin.json. Skills in in-progress/ and deprecated/ must not appear in either.
Each skill directory must contain a SKILL.md with name and description frontmatter.
Each bucket folder has a README.md listing its skills with one-line descriptions, with each skill name linked to its SKILL.md.
Additional reference files (e.g., setup.md, patterns.md) are placed alongside SKILL.md in the skill directory.
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.

