skills
AGENTS.md12 starsChanged 20 days agoMITView on GitHub
This is a single-context repo. GLOSSARY.md holds the domain language. Use its terms in code, docs, and replies. A new authored skill moves through two stages, in this order: The marker hides the skill from Skills CLI discovery. To test the skill while it is internal, install it by name: The Marketplace Manifest lists only Public Skills. An Internal Skill never appears in it. .agents/skills/ holds the Repository Skills that maintain this repo, and .claude/skills/ links to them. They belong…
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 repository12 other files it gives its agents.
- prSkill
- writing-for-agentsSkill
- adversarial-councilSkill
- diagnoseSkill
- explore-subagentsSkill
- github-writingSkill
- mise-reviewSkill
- optimize-skillSkill
- project-setupSkill
- prSkill
- t3-pr-review-webhookSkill
- audit-website-copySkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Internal Skill: Create the skill at skills/<collection>/<skill-name>/SKILL.md.
- Distinctive: line 22
Promotion: When the owner considers the skill ready, make both changes in the same commit:
- Very specific: line 23
Remove the internal marker from the frontmatter.
- Very specific: line 24
Add ./skills/<collection>/<skill-name> to the group of its Collection in .claude-plugin/marketplace.json.
≈ “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
Agents
This is a single-context repo. GLOSSARY.md holds the domain language. Use its terms in code, docs, and replies.
Skill lifecycle
A new authored skill moves through two stages, in this order:
Internal Skill. Create the skill at
skills/<collection>/<skill-name>/SKILL.md. Give itnameanddescriptionfrontmatter, and add this marker to the frontmatter:metadata: internal: trueThe marker hides the skill from Skills CLI discovery. To test the skill while it is internal, install it by name:
npx skills@latest add gabimoncha/skills --skill <skill-name>- Promotion. When the owner considers the skill ready, make both changes in the same commit:
- Remove the
internalmarker from the frontmatter. - Add
./skills/<collection>/<skill-name>to the group of its Collection in.claude-plugin/marketplace.json.
- Remove the
The Marketplace Manifest lists only Public Skills. An Internal Skill never appears in it.
Repository Skills
.agents/skills/ holds the Repository Skills that maintain this repo, and .claude/skills/ links to them. They belong to no Collection, so they stay out of the Marketplace Manifest.
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.

