Background
The Feb 26 office hours focused on building reference implementations for skills-as-resources. This issue covers the server side — a canonical example showing how to expose skills using existing MCP primitives (resources, tools, resource templates) without protocol changes.
This is distinct from #24 (NimbleBrain-specific approach) — this issue is about a minimal, framework-agnostic reference implementation that demonstrates the convention.
Scope
Build a reference MCP server that:
- Exposes skills as resources using a consistent URI scheme (e.g., skill://server-name/skill-name)
- Supports resources/list returning skill metadata (name, description, version)
- Supports resources/read returning full skill content (SKILL.md body)
- Optionally supports resources/subscribe and notifications/resources/updated for push-based updates
- Optionally exposes a list_skills tool as a model-controlled alternative
- Includes at least 2 example skills (one simple, one complex multi-step workflow)
- Uses server instructions to guide the model toward skill discovery
Acceptance Criteria
References
Background
The Feb 26 office hours focused on building reference implementations for skills-as-resources. This issue covers the server side — a canonical example showing how to expose skills using existing MCP primitives (resources, tools, resource templates) without protocol changes.
This is distinct from #24 (NimbleBrain-specific approach) — this issue is about a minimal, framework-agnostic reference implementation that demonstrates the convention.
Scope
Build a reference MCP server that:
Acceptance Criteria
References