skills
CLAUDE.md1 starsChanged 4 months agoMITView on GitHub
Agent instructions for this repo live in @AGENTS.md — read it first. It covers what this collection is, the layout, the frontmatter contract, the working commands (validate a skill, scan for org fingerprints), and the hard rules (100% validator score, name matches directory, one LICENSE per skill, clean conventional commits, don't commit local tooling). - skill-builder/SKILL.md — the authoring system: how to scaffold a spec-compliant skill, write a description that actually triggers, and split an oversized SKILL.md into references/. It…
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-auditSkill
- autodreamSkill
- deep-discoverySkill
- generic-by-designSkill
- gitops-cd-developerSkill
- gitops-pipeline-developerSkill
- golang-script-developerSkill
- humanizerSkill
- information-architectureSkill
- interactive-deck-builderSkill
- javascript-script-developerSkill
- linux-script-developerSkill
- makefile-script-developerSkill
- plan-interviewSkill
- pre-commit-setupSkill
- python-script-developerSkill
- qaSkill
- skill-builderSkill
- teacher-modeSkill
- terraform-module-developerSkill
- typescript-script-developerSkill
- ui-deslopSkill
- xquik-x-dataSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Keep this file thin: put durable instructions in AGENTS.md, not here.
≈ “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
Agent instructions for this repo live in @AGENTS.md — read it first. It covers what
this collection is, the layout, the frontmatter contract, the working commands (validate a
skill, scan for org fingerprints), and the hard rules (100% validator score, name matches
directory, one LICENSE per skill, clean conventional commits, don't commit local tooling).
Authoring context
skill-builder/SKILL.md— the authoring system: how to scaffold a spec-compliant skill, write a description that actually triggers, and split an oversizedSKILL.mdintoreferences/. It is a skill in this repo, so it is both the tool and the style guide.generic-by-design/SKILL.md— the pre-publish pass: what counts as an organization-specific fingerprint and what to replace it with.
Keep this file thin: put durable instructions in AGENTS.md, not here.
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.