agent-skills
AGENTS.md2 starsChanged 57 days agoMITView on GitHub
Read STRUCTURE.md for bundle rules and verification. Skills live at the root; D.A.V.E. retains its plugin-compatible nested path. Update README's catalog and run bash scripts/verify.sh when changing entries. Keep required assets inside selected bundles and declare sibling dependencies explicitly. Preserve user edits and state. Never run git push. Use focused Conventional Commits without co-author trailers unless requested. Do not install/update the user's personal skills as a side effect of source changes. Ask only for missing information that changes the result.…
- Commits and pushes
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,774 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 repository20 other files it gives its agents.
- accessibility-auditSkill
- app-designSkill
- cloudflare-temporary-deploySkill
- code-reviewSkill
- codex-delegateSkill
- commit-documentorSkill
- constructorSkill
- datasecurerSkill
- dependabot-validatorSkill
- dogfoodSkill
- flask-testsSkill
- ideatorSkill
- lan-viewerSkill
- memorySkill
- ollama-delegateSkill
- pr-grill-meSkill
- rest-graphql-debugSkill
- system-oneSkill
- web-pentestSkill
- workflow-rulesSkill
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
- Very specific: line 3
Read STRUCTURE.md for bundle rules and verification.
- Distinctive: line 12
Ask only for missing information that changes the result.
≈ “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 maintenance
Read STRUCTURE.md for bundle rules and verification. Skills live at the root;
D.A.V.E. retains its plugin-compatible nested path. Update README's catalog and
run bash scripts/verify.sh when changing entries. Keep required assets inside
selected bundles and declare sibling dependencies explicitly.
Preserve user edits and state. Never run git push. Use focused Conventional Commits without co-author trailers unless requested. Do not install/update the user's personal skills as a side effect of source changes.
Ask only for missing information that changes the result. Keep documentation and safeguards with their owner. Existing approved plans govern scope; record material deviations there. Use mock/loopback tests for external helpers.
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.