mattie_skills
AGENTS.md1 starsChanged 8 days agoMITView on GitHub
Placeholder for repository-specific agent guidance. Until this file is expanded, follow the applicable user and global agent instructions. This repository is intended to be published at Mattie/mattie_skills. - Store each independently invoked skill at skills/<skill-name>/. - Keep the canonical files for a skill in one directory. Harness manifests and distribution adapters should reference or package that directory without introducing maintained copies. - Keep coordinated skill sets as sibling directories under skills/. Document the shared workflow in docs/<set-name>.md and group shared…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository23 other files it gives its agents.
- aftermath-rewindSkill
- aiconographerSkill
- ask-socratesSkill
- check-project-nameSkill
- goal-checkSkill
- lean-proof-reviewSkill
- parallax-imageSkill
- prior-artSkill
- projectbotSkill
- quiet-uxSkill
- rmddSkill
- rmdsSkill
- rmdvSkill
- rrr-review-remedy-respondSkill
- soft-skill-creatorSkill
- thought-rigSkill
- todoSkill
- verifier-systemSkill
- what-huhSkill
- what-whatSkill
- write-humanlySkill
- write-plainlySkill
- write-simplified-technical-englishSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Keep the canonical files for a skill in one directory.
- Very specific: line 19
Keep coordinated skill sets as sibling directories under skills/.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
Repository Agent Instructions
Placeholder for repository-specific agent guidance.
Until this file is expanded, follow the applicable user and global agent instructions.
Repository destination
This repository is intended to be published at Mattie/mattie_skills.
Repository structure
- Store each independently invoked skill at
skills/<skill-name>/. - Keep the canonical files for a skill in one directory. Harness manifests and distribution adapters should reference or package that directory without introducing maintained copies.
- Keep coordinated skill sets as sibling directories under
skills/. Document the shared workflow indocs/<set-name>.mdand group shared tests undertests/<set-name>/.
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.