Define well-known URI schemes and naming patterns for skill resources (#53)
* Add skill URI scheme proposal with survey of existing patterns (#44) Survey 6 existing URI patterns (NimbleBrain, skilljack-mcp, skills-over-mcp, FastMCP 3.0, Cloudflare well-known RFC, SEP-2076) and propose a recommended skill:// URI convention for MCP skill resources. Cross-reference from approaches.md Approach 6. * Fix URI structure description: skill name is the authority, not a path segment * Add versioning deferral note and multi-server collision handling Address PR review feedback: note that versioning is intentionally deferred, and recommend clients provide a read_resource tool with server name for disambiguation when multiple servers expose the same skill URI.
This commit is contained in:
parent
4dcb59d6c0
commit
36c5abddb7
1 changed files with 346 additions and 1 deletions
|
|
@ -133,7 +133,7 @@ Use server instructions as a pointer to a resource: "If you need to do X, fetch
|
|||
|
||||
A documented "MCP Skills Convention" as a middle path between ad-hoc experiments and protocol extension. This could:
|
||||
|
||||
- Define well-known URI schemes or naming patterns (e.g., resources matching `**/SKILL.md`)
|
||||
- Define well-known URI schemes or naming patterns (e.g., resources matching `**/SKILL.md`). See [Skill URI Scheme Proposal](skill-uri-scheme.md) for a detailed survey and recommendation.
|
||||
- Recommend metadata structure (version, tags, dependencies) aligned with agentskills.io
|
||||
- Provide guidance on control model: resources for application-controlled, `skill()` tool for model-controlled
|
||||
- Be documented in MCP docs as a "Pattern" — not in protocol schema, but officially recommended
|
||||
|
|
|
|||
Loading…
Reference in a new issue