Skip to content

Define well-known URI schemes and naming patterns for skill resources#53

Merged
pja-ant merged 3 commits into
mainfrom
skill-uri-scheme-proposal
Mar 12, 2026
Merged

Define well-known URI schemes and naming patterns for skill resources#53
pja-ant merged 3 commits into
mainfrom
skill-uri-scheme-proposal

Conversation

@pja-ant

@pja-ant pja-ant commented Mar 5, 2026

Copy link
Copy Markdown
Contributor

Closes #44

Adds docs/skill-uri-scheme.md — a proposal for standardizing skill resource URI schemes in the MCP Skills Convention.

Survey

Surveys 6 existing patterns with pros/cons for each:

Pattern URI Scheme Sub-resources Templates Spec-compatible
NimbleBrain skill:// No No No
skilljack-mcp skill:// / collection Yes No
skills-over-mcp skill:// /document/ path Yes No
FastMCP 3.0 skill:// File paths Configurable Yes
Well-Known RFC https:// File paths N/A Yes
SEP-2076 N/A N/A N/A No

Key finding: all four MCP-native implementations independently converged on skill:// as the URI scheme.

Proposed Convention

  • Scheme: skill://
  • Structure: skill://skill-name/SKILL.md (SKILL.md explicit, matching Agent Skills spec directory model)
  • Sub-resources: Path-based (skill://my-skill/references/GUIDE.md)
  • Templates: skill://{skill_name}/SKILL.md and skill://{skill_name}/{+path}
  • Naming rules: Aligned with Agent Skills spec (lowercase alphanumeric + hyphens, 1-64 chars)

Example URIs

Use Case URI
Basic skill skill://git-workflow/SKILL.md
Supporting document skill://code-review/references/SECURITY.md
Supporting script skill://pdf-processing/scripts/extract.py

Acceptance Criteria from #44

  • Survey of at least 4 existing URI patterns with pros/cons (6 surveyed)
  • Proposed recommended URI scheme with rationale
  • At least 3 example URIs covering common cases
  • Cross-reference from approaches.md

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.
@pja-ant
pja-ant marked this pull request as ready for review March 5, 2026 12:22
@pja-ant
pja-ant requested a review from a team as a code owner March 5, 2026 12:22

@olaservo olaservo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @pja-ant ! I had a few questions but I think this captures the main conventions we've been gravitating towards.

Comment thread docs/skill-uri-scheme.md Outdated
Comment thread docs/skill-uri-scheme.md
Comment thread docs/skill-uri-scheme.md
pja-ant added 2 commits March 9, 2026 12:05
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.
@pja-ant
pja-ant merged commit 36c5abd into main Mar 12, 2026
olaservo added a commit that referenced this pull request Mar 13, 2026
Replace PR #53 links with relative references to the now-merged
skill-uri-scheme.md document.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
olaservo added a commit that referenced this pull request Apr 8, 2026
* Update skill-meta-keys.md to reference merged URI scheme doc

Replace PR #53 links with relative references to the now-merged
skill-uri-scheme.md document.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

* Refactor skilljack-mcp section and update notes on `_meta` keys for clarity

* Refocus _meta doc as scoping framework, not key recommendations

Address PR feedback: remove recommended keys that duplicate
frontmatter or belong at the plugin/distribution layer. Change
namespace to io.modelcontextprotocol.skills/. Establish scoping
principles for when _meta is appropriate vs frontmatter, annotations,
or distribution-layer mechanisms.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

* Add decision record: _meta reserved for MCP-transport concerns

Records the decision from PR #60 review that skill-level semantics
stay in frontmatter, _meta is for MCP-transport-specific metadata,
and no specific keys are recommended yet.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

---------

Co-authored-by: Claude Opus 4.6 <[email protected]>
olaservo added a commit that referenced this pull request Apr 13, 2026
* Update skill-meta-keys.md to reference merged URI scheme doc

Replace PR #53 links with relative references to the now-merged
skill-uri-scheme.md document.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

* Refactor skilljack-mcp section and update notes on `_meta` keys for clarity

* Refocus _meta doc as scoping framework, not key recommendations

Address PR feedback: remove recommended keys that duplicate
frontmatter or belong at the plugin/distribution layer. Change
namespace to io.modelcontextprotocol.skills/. Establish scoping
principles for when _meta is appropriate vs frontmatter, annotations,
or distribution-layer mechanisms.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

* Add decision record: _meta reserved for MCP-transport concerns

Records the decision from PR #60 review that skill-level semantics
stay in frontmatter, _meta is for MCP-transport-specific metadata,
and no specific keys are recommended yet.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

---------

Co-authored-by: Claude Opus 4.6 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define well-known URI schemes and naming patterns for skill resources

4 participants