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

[olaservo]

Background

Multiple implementations already use different URI patterns for skill resources. NimbleBrain uses skill://, others use file-path-based patterns like **/SKILL.md. Before the convention can be finalized, there needs to be agreement on the URI scheme.

Scope

1. Survey existing patterns:

   • NimbleBrain: skill://server-name/skill-name (see experimental-findings.md)
   • skilljack-mcp: tool-based pattern
   • Agent Skills Discovery RFC: /.well-known/skills/ with index.json
   • FastMCP 3.0: check gofastmcp.com/servers/providers/skills
   • skills-over-mcp (Keith Groves): resource-based pattern

2. Propose a recommended pattern considering:

   • Consistency with MCP resource URI conventions
   • Compatibility with resource templates for parameterized access
   • Ability to distinguish skills from other resources in resources/list
   • Human readability

3. Document the proposal with examples:

   • Single skill: skill:///my-skill
   • Versioned skill: skill:///my-skill?version=1.0
   • Skill from a specific domain: skill://example.com/my-skill
   • Resource template: skill:///{skill_name}

Acceptance Criteria

• Survey of at least 4 existing URI patterns with pros/cons
• Proposed recommended URI scheme with rationale
• At least 3 example URIs covering common cases
• PR to docs/approaches.md or a new section in the convention draft

References

• Approach 6 in docs/approaches.md
• NimbleBrain pattern in experimental-findings.md
• Agent Skills Discovery RFC