Enhance design principles and open questions documentation with community insights on skills as context and discoverability challenges
This commit is contained in:
parent
1a83dc6012
commit
4665899d89
1 changed files with 15 additions and 11 deletions
|
|
@ -9,6 +9,10 @@
|
|||
- **No discovery mechanism** — users installing MCP servers from a registry don't know if there's a corresponding skill they should also install
|
||||
- **Multi-server orchestration** — skills may need to coordinate tools from multiple servers, which doesn't fit the single-server instruction model
|
||||
|
||||
## Broader Context
|
||||
|
||||
Skills discoverability is a specific instance of a more general MCP challenge: context-as-resources discoverability and standardization of client host behavior around non-tool primitives. The ecosystem has largely optimized for tools, and patterns for how clients discover and consume other forms of context — including skills — remain underdeveloped. Solutions in this space are likely to have implications beyond skills alone.
|
||||
|
||||
## Key Use Cases
|
||||
|
||||
See [use-cases.md](use-cases.md) for detailed use cases and community input. In summary:
|
||||
|
|
|
|||
Loading…
Reference in a new issue