From 02c486e162ec0c9f9f3443512ec974aff6547ac8 Mon Sep 17 00:00:00 2001 From: Ola Hungerford Date: Fri, 24 Apr 2026 04:52:35 -0700 Subject: [PATCH] docs: link SEP-2640 across repo and tidy Related Work table (#90) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Update documentation for Skills Extension SEP and related resources - Revised links and descriptions in README.md to reflect the submitted Skills Extension SEP (PR #2640). - Updated current status in approaches.md to indicate submission of the Skills Extension SEP. - Clarified tracking information in open-questions.md regarding the Skills Extension SEP submission. - Adjusted related work in related-work.md to include the Skills Extension SEP and mark a rejected proposal. - Changed status in sep-draft-skills-extension.md to 'submitted' and updated author information. - Enhanced skill-uri-scheme.md to indicate the incorporation of feedback into the submitted Skills Extension SEP. * Move rejected SEP-2093 to the bottom of SEPs and Proposals table Keeps the list active-proposals-first so readers aren't distracted by the struck-out entry. 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) * Mark SEP-2076 as closed and move to the bottom of proposals table PR #2076 was closed without merge on 2026-02-24. 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) * Use SEP-2640 naming convention per MCP SEP guidelines Per https://modelcontextprotocol.io/community/sep-guidelines, a submitted SEP is named "SEP-". Rename in-repo references from "PR #2640" to "SEP-2640" and update the draft doc heading from the "SEP-0000" placeholder to "SEP-2640". Also mark Approach 1's SEP-2076 status as closed (2026-02-24, no sponsor found); approaches.md still listed it as "Draft, seeking sponsor". 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) * Fix SEP-2076 closure rationale Closure followed the WG's decision to first explore a convention-based approach using existing primitives, not a sponsor issue. 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) * Refine SEP-2640 description in README to clarify proposal details * Link issues and meeting notes in Open Questions README row 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) * Surface SEP-2640 in README and related-work table order README: move the Skills Extension SEP from the bottom of the Repository Contents table to sit after Approaches, matching the narrative flow (framing → options → proposal → supporting material). related-work.md: lead the SEPs and Proposals table with SEP-2640 (this WG's headline proposal), followed by the prerequisite PR #2527. 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) * Add 'Open work' link to README header pointing to open PRs Signals that alternative proposals, decisions, implementations, and other in-flight contributions are welcome — SEP-2640 is one direction, not the only one. 🦉 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.7 (1M context) --------- Co-authored-by: Claude Opus 4.7 (1M context) --- README.md | 5 +++-- docs/approaches.md | 4 ++-- docs/open-questions.md | 2 +- docs/related-work.md | 5 +++-- docs/sep-draft-skills-extension.md | 10 +++++----- docs/skill-uri-scheme.md | 2 +- 6 files changed, 15 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index cd48275..48fe900 100644 --- a/README.md +++ b/README.md @@ -6,6 +6,7 @@ **Project board:** [Skills Over MCP WG](https://github.com/orgs/modelcontextprotocol/projects/38/views/1) **Meeting notes:** [Skills Over MCP WG discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/categories/meeting-notes-skills-over-mcp-wg) **Discord:** [#skills-over-mcp-wg](https://discord.com/channels/1358869848138059966/1464745826629976084) +**Open work:** [Pull requests](https://github.com/modelcontextprotocol/experimental-ext-skills/pulls) — proposals, decisions, implementations, and other in-flight contributions welcome. ## Why Skills Over MCP? @@ -34,11 +35,11 @@ See [problem-statement.md](docs/problem-statement.md) for full details. | [Why Skills Over MCP?](docs/why-and-when.md) | Value proposition and decision guide | | [Use Cases](docs/use-cases.md) | Key use cases driving this work | | [Approaches](docs/approaches.md) | Approaches being explored (not mutually exclusive) | -| [Open Questions](docs/open-questions.md) | Unresolved questions with community input | +| [SEP-2640: Skills Extension](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640) | Proposal to serve skills over MCP via the Resources primitive. Original working draft: [`docs/sep-draft-skills-extension.md`](docs/sep-draft-skills-extension.md). Comments and review happen on the PR. | +| [Open Questions](docs/open-questions.md) | Unresolved questions with community input (see also [issues](https://github.com/modelcontextprotocol/experimental-ext-skills/issues) and [meeting notes](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/categories/meeting-notes-skills-over-mcp-wg)) | | [Experimental Findings](docs/experimental-findings.md) | Results from implementations and testing | | [Related Work](docs/related-work.md) | SEPs, implementations, and external resources | | [Decision Log](docs/decisions.md) | Record of key decisions with context and rationale | -| [Draft SEP: Skills Extension](docs/sep-draft-skills-extension.md) | Pre-submission SEP draft defining the `skill://` resource convention | ## Contributing diff --git a/docs/approaches.md b/docs/approaches.md index b00d516..c361dfb 100644 --- a/docs/approaches.md +++ b/docs/approaches.md @@ -17,7 +17,7 @@ Several design considerations are emerging from community discussion: The approaches below span a spectrum. At one end, skills become a first-class MCP primitive with dedicated protocol methods (Approach 1). At the other, existing primitives are used with documented conventions (Approach 6). A key question for this WG is whether convention can prove patterns before standardization — or whether the ecosystem needs protocol-level support to achieve reliable interoperability. These are not mutually exclusive; convention work can inform and de-risk a future protocol extension. -**Current status:** The convention approach (Approach 6) was pursued and quickly evolved into a formal Extensions Track SEP ([#69](https://github.com/modelcontextprotocol/experimental-ext-skills/pull/69)), building on convergence across 4+ independent `skill://` implementations. The SEP uses existing Resources primitives with zero protocol changes, positioning it between pure convention and a new primitive. See [#75](https://github.com/modelcontextprotocol/experimental-ext-skills/issues/75) for tracking. +**Current status:** The convention approach (Approach 6) was pursued and quickly evolved into a formal Extensions Track SEP ([#69](https://github.com/modelcontextprotocol/experimental-ext-skills/pull/69)), building on convergence across 4+ independent `skill://` implementations. The SEP uses existing Resources primitives with zero protocol changes, positioning it between pure convention and a new primitive. See [#75](https://github.com/modelcontextprotocol/experimental-ext-skills/issues/75) for tracking. Submitted to the MCP spec as [SEP-2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640) on 2026-04-23. ## 1. Skills as Distinct MCP Primitives @@ -35,7 +35,7 @@ Add Agent Skills as a first-class, discoverable primitive in MCP. A skill is a n - Progressive disclosure: clients load skill summaries at startup, fetch full instructions on demand - Mapping to existing SKILL.md format -**Status:** Draft, seeking sponsor. +**Status:** Closed on 2026-02-24 after the WG decided to first explore a convention-based approach using existing primitives. See [SEP-2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640) for the resulting Resources-based proposal. **Community input:** diff --git a/docs/open-questions.md b/docs/open-questions.md index 3339e7b..e4c4881 100644 --- a/docs/open-questions.md +++ b/docs/open-questions.md @@ -121,7 +121,7 @@ See also [Approaches](approaches.md) for more notes on using resources. ## 13. What is the optimal relationship between skills and MCP? -> **Tracked in:** [#75](https://github.com/modelcontextprotocol/experimental-ext-skills/issues/75) — Skills Extension SEP +> **Tracked in:** [#75](https://github.com/modelcontextprotocol/experimental-ext-skills/issues/75) — Skills Extension SEP (submitted as [SEP-2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640)) > **See also:** [#47](https://github.com/modelcontextprotocol/experimental-ext-skills/issues/47) — Create evaluation matrix mapping approaches to requirements Skills already work as simple files that agents load directly. Adding MCP to the process should provide clear value beyond what standalone skills already offer. diff --git a/docs/related-work.md b/docs/related-work.md index b186ca7..5bf692e 100644 --- a/docs/related-work.md +++ b/docs/related-work.md @@ -4,10 +4,11 @@ | Proposal | Venue | Description | | :--- | :--- | :--- | -| [SEP-2076](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2076) | MCP Spec | Agent Skills as a first-class MCP primitive | -| [SEP-2093](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2093) | MCP Spec | Resource Contents Metadata and Capabilities: scoped `resources/list`, per-resource capabilities, `resources/metadata` endpoint | +| [SEP-2640 (Skills Extension)](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640) | MCP Spec | This WG's proposed extension: skills served over MCP using the Resources primitive and `skill://` URI scheme ([working draft](sep-draft-skills-extension.md)) | | [PR #2527](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2527) | MCP Spec | Recommend clients expose resource read to models — prerequisite for the resources-based skills approach | | [skills.json format proposal](https://github.com/modelcontextprotocol/registry/discussions/895) | MCP Registry | Skills metadata in registry schema | +| ~~[SEP-2093](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2093)~~ | MCP Spec | ~~Resource Contents Metadata and Capabilities: scoped `resources/list`, per-resource capabilities, `resources/metadata` endpoint~~ — **rejected** ([labeled upstream](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2093)) | +| ~~[SEP-2076](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2076)~~ | MCP Spec | ~~Agent Skills as a first-class MCP primitive~~ — **closed** (2026-02-24, without merge) | ## Working Group Member Implementations diff --git a/docs/sep-draft-skills-extension.md b/docs/sep-draft-skills-extension.md index 799c604..a3b7475 100644 --- a/docs/sep-draft-skills-extension.md +++ b/docs/sep-draft-skills-extension.md @@ -1,14 +1,14 @@ -# SEP-0000: Skills Extension +# SEP-2640: Skills Extension -- **Status**: Draft (pre-submission) +- **Status**: Draft (submitted) - **Type**: Extensions Track - **Created**: 2026-03-17 -- **Author(s)**: Skills Over MCP Interest Group +- **Author(s)**: Skills Over MCP Working Group - **Sponsor**: _(seeking)_ - **Extension Identifier**: `io.modelcontextprotocol/skills` -- **PR**: _(to be assigned on submission)_ +- **PR**: [#2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640) -> This document is a pre-submission draft maintained by the [Skills Over MCP Interest Group](https://github.com/modelcontextprotocol/experimental-ext-skills). It has not yet been submitted to the main MCP repository. Discussion welcome via [GitHub Issues](https://github.com/modelcontextprotocol/experimental-ext-skills/issues) or [Discord #skills-over-mcp-ig](https://discord.com/channels/1358869848138059966/1464745826629976084). +> **NOTE:** This SEP has been submitted to the main MCP repository as [SEP-2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640); future review and comments happen there. This repo-local copy is the working draft maintained by the [Skills Over MCP Working Group](https://github.com/modelcontextprotocol/experimental-ext-skills) and may be revised as upstream review feedback is incorporated. Additional discussion welcome via [GitHub Issues](https://github.com/modelcontextprotocol/experimental-ext-skills/issues) or [Discord #skills-over-mcp-wg](https://discord.com/channels/1358869848138059966/1464745826629976084). ## Abstract diff --git a/docs/skill-uri-scheme.md b/docs/skill-uri-scheme.md index cfd5a42..5806d15 100644 --- a/docs/skill-uri-scheme.md +++ b/docs/skill-uri-scheme.md @@ -3,7 +3,7 @@ > Proposed convention for identifying skill resources over MCP. **Issue:** [#44](https://github.com/modelcontextprotocol/experimental-ext-skills/issues/44) -**Status:** Incorporated into the draft [Skills Extension SEP](https://github.com/modelcontextprotocol/experimental-ext-skills/pull/69). This survey informed the SEP's URI scheme design; see also [PR #70](https://github.com/modelcontextprotocol/experimental-ext-skills/pull/70) for subsequent refinements (multi-segment paths, path-name decoupling). +**Status:** Incorporated into the draft [Skills Extension SEP](https://github.com/modelcontextprotocol/experimental-ext-skills/pull/69), now submitted to the MCP spec as [SEP-2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640). This survey informed the SEP's URI scheme design; see also [PR #70](https://github.com/modelcontextprotocol/experimental-ext-skills/pull/70) for subsequent refinements (multi-segment paths, path-name decoupling). ---