agent-skills
AGENTS.md4 starsChanged 7 months agoMITView on GitHub
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 repository42 other files it gives its agents.
- agent-soulSkill
- audit-transcripts-for-learningsSkill
- best-answerSkill
- check-coherenceSkill
- compress-fileSkill
- deep-modulesSkill
- design-critiqueSkill
- durable-docs-updateSkill
- execute-chatSkill
- execute-planSkill
- explain-deeplySkill
- explain-simplySkill
- find-gapsSkill
- fix-verify-loopSkill
- generate-mockupsSkill
- grill-meSkill
- handoffSkill
- interview-meSkill
- jtbdSkill
- map-design-languageSkill
- memory-pruneSkill
- multi-agent-analysisSkill
- place-factSkill
- post-purchase-ui-extensionSkill
- product-interviewSkill
- prove-behaviorSkill
- refine-fileSkill
- second-opinionSkill
- sentry-analysisSkill
- shopify-dev-mcpSkill
- structure-proseSkill
- tech-designSkill
- test-completed-planSkill
- tighten-fileSkill
- tighten-instructionSkill
- tldrSkill
- triageSkill
- trim-specSkill
- two-pass-reviewSkill
- validate-answerSkill
- vet-factSkill
- write-planSkill
The file
We split this AGENTS.md into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Read WRITING-GUIDE.md before authoring or editing a skill or agent.
- Distinctive: line 6
Write skill files and other instructions for reliable AI execution: make each instruction clear, coherent, explicit, and actionable without …
- Distinctive: line 7
Before reporting an instruction-text edit complete, invoke these skills (the lenses) in order:
- Very specific: line 15
When updating a shared schema in references/, sync all consumers per WRITING-GUIDE.md.
- Very specific: line 16
When a skill/agent/command is added, removed, or renamed, sync both the README.md list and .claude-plugin/plugin.json's skills array to …
- Very specific: line 17
When a skill/agent/command's purpose changes, update its README.md description.
- Very specific: line 21
Run scripts/validate-skills.sh once when I ask to commit.
- Very specific: line 22
After a commit that adds or updates a skill/agent/command, offer to install the changed ones based on the instructions below:
≈ “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
Agent Skills Repo
Authoring
- Read
WRITING-GUIDE.mdbefore authoring or editing a skill or agent. - Write skill files and other instructions for reliable AI execution: make each instruction clear, coherent, explicit, and actionable without relying on human inference.
- Before reporting an instruction-text edit complete, invoke these skills (the lenses) in order:
- On a file created this run, invoke the
compress-fileskill via the Skill tool. - Invoke the
tighten-instructionskill, then thestructure-proseskill, via the Skill tool. - Invoke the
check-coherenceskill via the Skill tool.
- On a file created this run, invoke the
- Apply a lens change only when it materially improves instruction clarity or reliable execution, has confidence ≥ 0.80, and preserves every instruction's meaning.
Sync on change
- When updating a shared schema in
references/, sync all consumers perWRITING-GUIDE.md. - When a skill/agent/command is added, removed, or renamed, sync both the
README.mdlist and.claude-plugin/plugin.json'sskillsarray to matchskills/— alphabetical order. - When a skill/agent/command's purpose changes, update its
README.mddescription.
Commit & install
- Run
scripts/validate-skills.shonce when I ask to commit. - After a commit that adds or updates a skill/agent/command, offer to install the changed ones based on the instructions below:
| Type | Install |
| Skill | run npx skills add preetamnath/agent-skills --skill <changed names> (prefill the names) |
| Agent | copy agents/<name>.md → ~/.claude/agents/<name>.md |
| Command | copy commands/<name>/<name>.md → ~/.claude/commands/<name>.md (flat — no subdir) |
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.

