ext-skills
AGENTS.md755 starsChanged 16 days agoApache-2.0View on GitHub
IMPORTANT: The source of truth for the Skills extension (io.modelcontextprotocol/skills) is specification/beta/skills.mdx in this repository. It is the normative text of the extension, written against base protocol revision 2026-07-28, and is what the official documentation at modelcontextprotocol.io/extensions/skills/overview summarizes. SEP-2640 is the accepted proposal behind the extension (Status: Final; PR #2640 merged 2026-09-13). docs/archive/sep-draft-skills-extension.md is a copy of that SEP text pinned at the commit named in its header, kept so Working Group discussion, meeting notes, and decision records can quote…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- modelcontextprotocol/experimental-ext-skillsword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- modelcontextprotocol/experimental-ext-skills★ 756100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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,542 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 16
When a decision supersedes or amends an earlier one, add a forward pointer to the earlier entry's Status: line rather than rewriting the …
≈ “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
What to reference as a source
IMPORTANT: The source of truth for the Skills extension (io.modelcontextprotocol/skills) is specification/beta/skills.mdx in this repository. It is the normative text of the extension, written against base protocol revision 2026-07-28, and is what the official documentation at modelcontextprotocol.io/extensions/skills/overview summarizes.
SEP-2640 is the accepted proposal behind the extension (Status: Final; PR #2640 merged 2026-09-13). docs/archive/sep-draft-skills-extension.md is a copy of that SEP text pinned at the commit named in its header, kept so Working Group discussion, meeting notes, and decision records can quote and link stable text. It is a historical baseline, not the current spec.
- Answer questions about what the extension requires from
specification/beta/skills.mdx, not from the SEP copy or thedocs/folder. Where the spec page and the SEP differ, the decision log records why (see the 2026-09-08 entry). - The
docs/folder holds design history, rationale, experimental findings, and trackers. Treat it as context, not as normative text.
Proposing changes to the specification
Changes are proposed here. The vehicle is a dated entry in docs/decisions.md with **Status:** Proposed, in the ADR-lite format used throughout that file (Status / Context / Decision / Rationale / References) — the PR carrying that entry is the proposal.
specification/beta/skills.mdx is a released revision and is not edited in place. Once a proposal is accepted, the resulting text lands in a draft revision of the specification (a draft/ directory alongside the released text, following the layout used by ext-tasks), the entry's status is updated to Accepted, and the draft ships as a new revision when released. The extension is at the Beta stage of the extension lifecycle, so a revision may make breaking changes; each breaking change is recorded in the decision log.
When a decision supersedes or amends an earlier one, add a forward pointer to the earlier entry's **Status:** line rather than rewriting the entry. The log is an auditable trace of the group's reasoning over time, not a snapshot of current state.
See CONTRIBUTING.md for participation, meetings, decision-making authority, and full decision-log guidance.
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.