search_skills

This commit is contained in:
John Lancaster
2026-08-08 00:14:31 -05:00
parent 9be7c27410
commit 6ec12a100a
7 changed files with 196 additions and 16 deletions
+3 -3
View File
@@ -53,15 +53,15 @@ These utilities operate directly on the native `skill://` contract and require n
In VS Code, skills can arrive through:
1. explicit attachment from `Add Context > MCP Resources` or `MCP: Browse Resources`
2. the generic `list_resources` and `read_resource` tools for autonomous agents
2. the `search_skills` and `read_resource` tools for autonomous agents
3. a slash-command prompt that names a specific native skill URI
Instructions can steer retrieval, but they do not guarantee automatic resource attachment in every chat surface. When the deferred-tool catalog omits direct MCP resource operations, use the generic tools; they delegate to the native providers and do not duplicate skill metadata or content.
Instructions can steer retrieval, but they do not guarantee automatic resource attachment in every chat surface. When the deferred-tool catalog omits direct MCP resource operations, use the tools; search derives matches from native provider metadata and `read_resource` delegates to the provider without duplicating skill content.
A reliable prompt is:
```text
Call list_resources and select the best matching skill://.../SKILL.md resource. Use read_resource for one selected skill, inspect its _manifest only if supporting detail is needed, and reconcile the guidance with this workspace.
Call search_skills with the task or capability and select the best matching skill://.../SKILL.md result. Use read_resource for one selected skill, inspect its _manifest only if supporting detail is needed, and reconcile the guidance with this workspace.
```
## Thin Shim Pattern