Skip to content

Update URI scheme proposal to decouple path from skill name#70

Open
pja-ant wants to merge 1 commit intomainfrom
update-uri-scheme-path-based
Open

Update URI scheme proposal to decouple path from skill name#70
pja-ant wants to merge 1 commit intomainfrom
update-uri-scheme-path-based

Conversation

@pja-ant
Copy link
Contributor

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

Aligns the proposed convention with the draft SEP:

  • skill-path is a locator of one or more segments, not the skill name; identity lives in SKILL.md frontmatter
  • authority component is the first path segment by RFC 3986 mechanics but carries no special semantics
  • add no-nesting constraint (SKILL.md cannot be ancestor of another)
  • resource templates are MAY and primarily user-facing via completion
  • enumeration via resources/list is optional; clients must not treat an empty list as proof of absence
  • add nested-path examples throughout

The survey section is unchanged; it's historical record.

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

Aligns the proposed convention with the draft SEP:

- skill-path is a locator of one or more segments, not the skill name;
  identity lives in SKILL.md frontmatter
- authority component is the first path segment by RFC 3986 mechanics
  but carries no special semantics
- add no-nesting constraint (SKILL.md cannot be ancestor of another)
- resource templates are MAY and primarily user-facing via completion
- enumeration via resources/list is optional; clients must not treat
  an empty list as proof of absence
- add nested-path examples throughout

The survey section is unchanged; it's historical record.
@pja-ant pja-ant requested a review from a team March 18, 2026 11:24
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.

1 participant