agent-skills
AGENTS.md0 starsChanged 42 days agoMITView on GitHub
Keep distributed skills independent of any individual's machine, account, private project, or task system. User profiles belong outside the repository and installed skill directories. Generic examples use placeholders. Follow CONTRIBUTING.md for layout, versioning, checks, and releases. Maintain each skill's documented contracts, such as its profile format, explicit invocation, and project ownership rules. A profile customizes a workflow; it does not grant additional permissions. Run npm run check before committing. Review every staged file for personal information and private integration details.…
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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- cold-readSkill
- session-context-closeSkill
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 3
Keep distributed skills independent of any individual's machine, account, private project, or task system.
- Distinctive: line 5
Follow CONTRIBUTING.md for layout, versioning, checks, and releases.
- Very specific: line 7
Run npm run check before committing.
≈ “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
Maintaining this collection
Keep distributed skills independent of any individual's machine, account, private project, or task system. User profiles belong outside the repository and installed skill directories. Generic examples use placeholders.
Follow CONTRIBUTING.md for layout, versioning, checks, and releases. Maintain each skill's documented contracts, such as its profile format, explicit invocation, and project ownership rules. A profile customizes a workflow; it does not grant additional permissions.
Run npm run check before committing. Review every staged file for personal information and private integration details. Use explicit staged paths. Commit with a GitHub noreply email, never a personal address. Do not change repository visibility or settings as part of a routine update.
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.