skills
AGENTS.md2 starsChanged 29 days agoMITView on GitHub
When adding or changing a skill or its supporting files, follow the metadata policy for author and date-version updates. When changing public Markdown, file paths, headings, or the reference checker, follow repository validation before reporting completion. Check the complete candidate tree, including unchanged reference sources. For skill evolution, renames, retirement, and history migration, follow the repository history policy. Detailed history stays local; selected summaries are tracked after publication review. Execution environments and migration quarantine stay ignored. Issues and specs are…
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 32,671 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 repository18 other files it gives its agents.
- assess-findingsSkill
- browse-recordsSkill
- challenge-the-claimSkill
- evolve-skillsSkill
- expand-the-frameSkill
- explore-new-capabilitiesSkill
- get-up-to-speedSkill
- implement-changeSkill
- investigate-with-evidenceSkill
- issue-writingSkill
- just-use-itSkill
- make-it-landSkill
- prune-the-treeSkill
- review-changeSkill
- set-theory-for-projectsSkill
- setup-sakana-skillsSkill
- tool-fit-for-projectsSkill
- yak-shaving-triageSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 5
When adding or changing a skill or its supporting files, follow the metadata policy for author and date-version updates.
- Distinctive: line 9
When changing public Markdown, file paths, headings, or the reference checker, follow repository validation before reporting completion.
- Very specific: line 21
Use the five canonical triage labels without overrides.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
Agent skills
Skill metadata
When adding or changing a skill or its supporting files, follow the metadata policy for author and date-version updates.
Repository validation
When changing public Markdown, file paths, headings, or the reference checker, follow repository validation before reporting completion. Check the complete candidate tree, including unchanged reference sources.
Evolution records
For skill evolution, renames, retirement, and history migration, follow the repository history policy. Detailed history stays local; selected summaries are tracked after publication review. Execution environments and migration quarantine stay ignored.
Issue tracker
Issues and specs are tracked in GitHub Issues using the gh CLI. See docs/agents/issue-tracker.md.
Triage labels
Use the five canonical triage labels without overrides. See docs/agents/triage-labels.md.
Domain docs
This repo uses the single-context layout: root CONTEXT.md and docs/adr/. See docs/agents/domain.md.
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.

