c00ca72d94* docs: sync repo SEP copy with canonical v1 text The repo-local copy of SEP-2640 had drifted well behind the canonical text on the sep/skills-extension branch, which was a source of confusion: it still specified the well-known skill://index.json resource and predated skills/list, skills/get, resources/directory/read, nested skills, and per-file digests. Replace the body with a verbatim copy of the canonical SEP as of d7490ec (2026-07-15) and swap the stale "not actively maintained" notice for a disclaimer that states what this file now is: a synced snapshot, re-synced by overwriting rather than hand-editing, with review on the upstream PR and anything beyond v1 raised as a PR in this repository. Also drop "working draft" from the README and related-work references to this file, since it is no longer where the text is drafted. * docs: frame the SEP copy as the v1 baseline for decision-log proposals The previous note told readers not to propose changes here at all, which is the wrong instruction: the WG does want to propose beyond v1, just in this repo rather than on the upstream SEP. Reframe the file as the v1 baseline and route proposals through the existing decision log rather than a parallel mechanism. decisions.md already carries the ADR-lite format, the Proposed/Accepted/Superseded status idiom, and the precedent for consolidating a version's scope into one record (the 2026-07-16 v1 entry), so a change beyond v1 is simply the next dated entry. The note also defines the marker that ties an amended section back to its record, so v1 text stays distinguishable from accepted deltas as the document accumulates them. Align the README and related-work references to the same framing. * docs: mark the 2026-04-16 URI decision superseded in part Every other decision the v1 scope-down changed carries a forward pointer in its status line (2026-04-19, 2026-06-02, 2026-06-05, 2026-06-09). The 2026-04-16 URI entry was left as plain Accepted while three of its bullets no longer hold, so it reads as current guidance for index.json enumeration and the no-nesting rule. Give it the same treatment, naming which bullets changed and which parts of the URI convention carry forward, so the entry stays useful as a record of the structure it settled. * docs: add AGENTS.md and make the SEP PR link prominent Readers were landing on the repo-local SEP copy and taking it for the spec, which is how the stale version misled people in the first place. Say plainly, in the places they land, that the v1 spec text lives on modelcontextprotocol#2640: - README: a source-of-truth line at the top of the link block, above the charter. - The baseline copy: lead the header note with the PR rather than mentioning it mid-paragraph. - AGENTS.md: state the rule for agents working in this repo, along with how to propose beyond v1 via the decision log and the repo's markdown conventions. CLAUDE.md is a one-line pointer to AGENTS.md rather than a symlink, so it resolves on Windows checkouts too, where symlinks need Developer Mode and would otherwise land as a stub. * docs: use the @AGENTS.md import in CLAUDE.md A markdown link is not an import — Claude Code would have loaded the pointer line and never expanded AGENTS.md into context. The documented syntax is @path, which the docs specifically recommend over a symlink on Windows, where symlinks need Administrator privileges or Developer Mode. The maintainer note is a block-level HTML comment, which Claude Code strips before injecting the file, so it costs no context while staying visible to anyone opening the file. https://code.claude.com/docs/en/memory#agents-md * docs: tighten AGENTS.md to the source-of-truth rule Cut the project overview and conventions sections and lead with what an agent most needs to get right: the v1 spec text is on the PR, and the copy here is only as current as its pinned commit. CONTRIBUTING.md already covers participation and process.
17 lines
1.9 KiB
Markdown
17 lines
1.9 KiB
Markdown
## What to reference as a source
|
|
|
|
**IMPORTANT**: The v1 SEP source of truth is the PR, not this repository. The specification text for the Skills Extension lives on **[SEP-2640](https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2640)** (`modelcontextprotocol/modelcontextprotocol`, branch [`sep/skills-extension`](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/sep/skills-extension/seps/2640-skills-extension.md)). That PR is authoritative.
|
|
|
|
[`docs/sep-draft-skills-extension.md`](docs/sep-draft-skills-extension.md) is a verbatim copy of the v1 baseline, synced from that branch at a commit pinned in the file's header. It exists so Working Group discussion, meeting notes, and decision records can quote and link stable text.
|
|
|
|
- **Do not answer questions about what the spec says from this repository alone.** The copy is only as current as its last sync — check the pinned commit in the file header against the canonical branch before relying on it.
|
|
|
|
## Proposing changes beyond v1
|
|
|
|
Changes beyond v1 are proposed here rather than added to the upstream SEP. The vehicle is a dated entry in [`docs/decisions.md`](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.
|
|
|
|
Once a proposal is accepted, the resulting spec text is applied to the baseline copy and that section is marked with a pointer back to its record. A section without such a marker is v1 as it stands upstream.
|
|
|
|
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](CONTRIBUTING.md) for participation, meetings, decision-making authority, and full decision-log guidance.
|