* docs: point README and AGENTS.md at the released spec and official docs
SEP-2640 is Final and the extension ships from specification/stable/skills.mdx,
so the README now leads with a Specification section linking the spec file,
the official docs page (modelcontextprotocol.io/extensions/skills/overview),
the published SEP, and the client matrix. The experimental banner is replaced
with a note that docs/ holds working documents; the charter, pulls, and issues
links move off the redirecting experimental-ext-skills / charter URLs.
AGENTS.md no longer names the SEP PR as the source of truth; it points agents
at the stable spec page and describes the decision-log flow against that file.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: accepted spec changes land in a draft revision, not the stable file
The stable specification is a released snapshot. README and AGENTS.md now say
accepted decision-log proposals go into a draft revision that ships as a new
release, matching the ext-tasks specification layout.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: move pre-release design documents to docs/archive
SEP-2640 is Final, so docs/ now holds only living working documents. Eight
historical documents move to docs/archive with an index explaining what each
was and what superseded it: the SEP baseline copy, why-and-when, use-cases,
approaches, skill-uri-scheme, glossary, client-mcp-support (superseded by the
official client matrix), and agent-plugins-analysis.
Files the published SEP links to by path (decisions, experimental-findings,
open-questions, problem-statement, rationale, related-work, skill-meta-keys)
stay in place so those links keep working. Cross-links are rewritten and
verified; the README contents table is trimmed to match.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: archive open-questions and skill-meta-keys
Both are pre-release documents whose outcomes live in the decision log and
the specification. The published SEP links to them by path; a companion
change in modelcontextprotocol/modelcontextprotocol repoints those links.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: fix sibling links inside archived open-questions and skill-meta-keys
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: keep only the decision log and rationale in docs/
threat-model, experimental-findings, findings-template, problem-statement,
and related-work move to docs/archive with index rows. The candidates
tracker and the archived client-support survey are removed in favor of the
official extension client matrix, and links to them are repointed there.
README drops the Why and Problem Statement sections, which duplicate the
SEP's Motivation and the official overview page. CONTRIBUTING routes new
implementation findings to GitHub issues.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: fix sibling links inside newly archived documents
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: add a concise implementations list
One table each for servers/SDKs and hosts, one line per entry, replacing the
retired candidates tracker and the related-work implementation tables. Seeded
from those plus PR #141 and issue #144.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: put tracking links in the Status column of the implementations list
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: add a vendor/community category to the implementations list
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: replace the interim reference package with the TypeScript SDK row
The @olaservo/ext-skills package is retired in favor of first-class skills
APIs in the TypeScript SDK (typescript-sdk#2798, phase 1 in #2818). The
archived related-work page now points at implementations.md for current
information.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: drop pre-SEP rows from the implementations list
They are already recorded in the archived related-work page; the list now
points there instead. FastMCP stays because its row tracks the migration to v1.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: add official SDK progress, Tachyon, and Inspector 2.6.0 to implementations
From the WG Discord channel and the SDK repos as of 2026-09-15: Go, TypeScript,
Python, and C# SDKs all have open SEP-2640 PRs (Go passes conformance); the
conformance suite merged; Inspector 2.6.0 shipped skills verification; Tachyon
reports a server implementation. Adds an "in progress" status for open PRs.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: track Goose host support via the official issue
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: only tag community rows in the implementations list
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: tag MCP-project rows as official in the implementations list
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: split the implementations list into SDKs, servers, and hosts
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* docs: add MCPJam Inspector to hosts
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Revise implementations table format and content
Updated the implementations table to include language and status columns.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Correct links and clarify documentation references
Updated links to SEP-2640 and clarified document references.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: Sambhav Kothari <sambhavs.email@gmail.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Add standalone prototype for issue #66 (skill:// discovery/loading)
Builds a from-scratch MCP server + client per the merged SEP-2640 draft
(resources + skill://index.json, no custom methods), exercising flat and
nested skill paths, relative sub-resource references, and the
"enumeration is optional but direct read must still work" baseline.
Findings recorded in docs/experimental-findings.md.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Trim prototype to essentials
Inline the four skill fixture files into server.mjs (the prototype
demonstrates the transport binding, not filesystem loading) and drop the
prototype README, whose content is already in the PR description.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Add findings from VS Code SEP-2640 skill discovery implementation
Records what implementing skill:// discovery in VS Code proper surfaced:
the client already had the full progressive-disclosure loop and only
lacked an MCP source, its mcp-resource:// FS provider means the loading
half needs no code at all, and a new skill source touches more type
surfaces than expected.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Drop prototype code; keep findings only
experimental-ext-skills is a working-group docs repo, so a runnable
Node server/client pair did not belong in it. The actual client-side
implementation for issue #66 now lives in VS Code, and what belongs
here is the write-up of what that surfaced.
Folds the still-transferable observations from the removed prototype
(URI- vs metadata-based identification per #54, and the index digest
doc inconsistency) into the VS Code findings entry.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Add findings from running the VS Code integration against a live server
Records what surfaced once the implementation was run from a source
build against the Hugging Face MCP server, rather than only
type-checked: the index wire format had already moved past the
checked-in draft, per-context-computation discovery is an easy
accidental DoS, a new skill source touches four type surfaces that must
agree, and cross-server name collisions are unspecified by the SEP.
None of the three defects were caught by tsc or the unit tests.
Also corrects the previous entry, which said the work was not verified
against a running server — it now is, for discovery. Model invocation
remains undemonstrated and is called out as such.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Tighten the issue #66 findings entry
Cut ~half the words to match the length of neighbouring entries and
make it reviewable at a glance. Same findings, less prose.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Link the findings entry to the VS Code implementation PR
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* Restore the #54 identification note and reframe the digest point
Issue #66 asks explicitly for a URI- vs metadata-based identification
evaluation, so that belongs in the entry. The digest note is reframed
from a doc nitpick into the actionable version: the live server sends a
digest and this client ignores it, so nothing verifies skill integrity.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* docs: note VS Code findings were written against the pre-v1 draft
---------
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: olaservo <olahungerford@gmail.com>
* docs(findings): add PHP MCP SDK + Symfony AI Mate skills-as-resources entry
First PHP-ecosystem implementation of SEP-2640: php-sdk#372 serves a
directory of SKILL.md files as skill:// resources, symfony/ai#2132 ships
the skill content in the Mate MCP server. Records what was verified
(serving via MCP Inspector snapshots), the spec-text frictions hit
(_meta namespace, resource name charset, empty-payload serialization),
and the Claude Code consumption gap.
* docs(findings): reframe _meta and resource-name notes per SEP-2640 review
The SEP PR specifies the io.modelcontextprotocol.skills/ _meta prefix
(our SDK independently converged on it); the resource-name point is an
SDK registration-uniqueness detail, not a spec gap. Reframe both and
note the PR-vs-repo-draft drift on the _meta sentence.
* docs: note PHP SDK findings were written against the pre-v1 draft
---------
Co-authored-by: olaservo <olahungerford@gmail.com>
* docs: link Sam Morrow's Progressive Discovery in MCP (Part 2)
* docs: link Angie Jones's "Skills Over MCP" article
* docs: mark open-questions and experimental-findings as not actively maintained
* docs: soften approaches doc and mark SEP working draft as not actively maintained
* Add community insights from Discord threads and meeting notes
Distill Discord discussions (Feb 14-24) and Feb 26 office hours into
existing docs:
- New findings: NimbleBrain skill:// resource consolidation, skill
reliability/adherence issues across implementations
- Expanded approaches with distribution/provenance considerations,
resources adoption insight, and domain-level discovery (.well-known)
- Expanded open questions on dependencies and distribution trust
- Added Cloudflare Agent Skills Discovery RFC and NimbleBrain
reference implementations to related work
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Remove trust note since its already mentioned in the doc separately
* Clarify attribution for community insights on skill dependencies in open questions
* Refine findings on model skill adherence and community workarounds
* Remove outdated comparison section and streamline evaluation insights in experimental findings
* Remove unnecessary blank line in experimental findings documentation
* Add SEP-2093 proposal to related work documentation
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
