- MDX 96.1%
- TypeScript 3.9%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
8d60258eaa* docs: transition from Interest Group to Working Group Follow-up to modelcontextprotocol/modelcontextprotocol#2586, which converted the charter from IG to WG. - Rename Interest Group → Working Group in headings and prose - Update Discord (#skills-over-mcp-wg) and Discussions (meeting-notes-skills-over-mcp-wg) references; channel renames coordinated separately - CONTRIBUTING.md: align meeting norms with MCP group governance (7-day advance notice, meet.modelcontextprotocol.io) and rewrite Decision-Making to reflect WG authority (lazy consensus → formal vote → escalation), linking to the charter's Authority table - Keep CODEOWNERS team at skills-over-mcp-ig pending access-repo rename; TODO comment added - decisions.md: update present-tense preamble, log the IG → WG transition as a new ADR entry, and preserve historical entries Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(contributing): link to governance/charter instead of duplicating Meetings and Decision-Making sections now point to the MCP group governance doc and charter for canonical rules, keeping only the repo- or group-specific bits (notes location, coordination channels, outputs list). Also drops a leftover "rough consensus" IG-era phrase in the Decision Log guidelines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(codeowners): fix sentence fragment in default-owner comment "Has day-to-day governance" read as an incomplete sentence and overstated what CODEOWNERS actually encodes (review routing, not governance). Replace with a direct one-liner. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
| .github | ||
| docs | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
Skills Over MCP Working Group
⚠️ Experimental — This repository is an incubation space for the Skills Over MCP Working Group. Contents are exploratory and do not represent official MCP specifications or recommendations.
Charter: modelcontextprotocol.io/community/skills-over-mcp/charter — mission, scope, membership, active work items, and success criteria. Project board: Skills Over MCP WG Meeting notes: Skills Over MCP WG discussions Discord: #skills-over-mcp-wg
Why Skills Over MCP?
MCP servers give agents tools, but tools alone are insufficient for complex workflows — tool descriptions tell an agent what a tool does, not how to orchestrate multiple tools to achieve a goal. Skills bridge this gap. They are structured "how-to" knowledge: multi-step workflows, conditional logic, and orchestration instructions that can run to hundreds of lines.
Skills are context, and MCP is a context protocol. Agents already connect to remote services over MCP to get tools — they can get the know-how to use those tools through the same channel. A remote MCP server can serve both its tools and the instructions for using them together, as a single atomic unit. This also enables automatic discovery (connect to a server, find its skills), dynamic updates (server-side changes flow without reinstall), multi-server composition (skills orchestrating tools across servers), and enterprise distribution (RBAC, multi-tenant, version-adaptive content) — all through infrastructure MCP servers already provide.
See why-and-when.md for the full value proposition and a guide for when MCP distribution applies vs. simpler alternatives.
Problem Statement
Native "skills" support in host applications demonstrates demand for rich workflow instructions, but there's no convention for exposing equivalent functionality through MCP primitives. Current limitations include:
- Server instructions load only at initialization — new or updated skills require re-initializing the server
- Complex workflows exceed practical instruction size — some skills require hundreds of lines of markdown with references to bundled files
- No discovery mechanism — users installing MCP servers don't know if there's a corresponding skill they should also install
- Multi-server orchestration — skills may need to coordinate tools from multiple servers
See problem-statement.md for full details.
Repository Contents
| Document | Description |
|---|---|
| Problem Statement | Current limitations and gaps |
| Why Skills Over MCP? | Value proposition and decision guide |
| Use Cases | Key use cases driving this work |
| Approaches | Approaches being explored (not mutually exclusive) |
| Open Questions | Unresolved questions with community input |
| Experimental Findings | Results from implementations and testing |
| Related Work | SEPs, implementations, and external resources |
| Decision Log | Record of key decisions with context and rationale |
Contributing
See CONTRIBUTING.md for how to participate.