john/prompts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

migration

Browse Source
This commit is contained in:
John Lancaster
2026-08-07 20:07:21 -05:00
parent 2a2700b78c
commit 5b6d5aaec4
70 changed files with 1182 additions and 3633 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/copilot.md
+3 -21
View File
@@ -6,7 +6,7 @@ icon: lucide/bot
## Purpose
This page explains how GitHub Copilot in VS Code consumes native skill resources from `personal-mcp`, including sessions where tools are visible but resource attachment is not.
This page explains how GitHub Copilot in VS Code consumes native skill resources and prompts from `personal-mcp`.
## Capability Lanes
@@ -16,7 +16,7 @@ Copilot interacts with MCP servers through independently exposed lanes:
2. resources attached as read-only context
3. server-provided prompts
This server publishes skills as native `skill://` resources, prompts through registry-backed resources and MCP prompt objects, and generic resource fallback tools through FastMCP.
This server publishes skills as native `skill://` resources and prompts as native MCP prompt objects.
## Native Skill Resources
@@ -39,22 +39,11 @@ A successful `resources/list` response does not guarantee the picker appears in
## Recommended Workflow
When resource attachment is available:
1. browse the server's resources
2. attach one relevant `skill://<name>/SKILL.md`
3. attach `_manifest` only if supporting detail may be needed
4. attach only selected supporting files
When only tools are available:
1. call `list_resources`
2. select a native main skill URI by name and description
3. call `read_resource` for that URI
4. read `_manifest` and supporting files only as needed
Both paths resolve through the same FastMCP provider.
## Prompt Examples
Resource attachment:
@@ -63,12 +52,6 @@ Resource attachment:
Use the attached personal-mcp skill as guidance, then reconcile it with the repository before proposing changes.
```
Tool-only discovery:
```text
Call list_resources, choose the best matching skill://.../SKILL.md resource, and read it. Inspect its _manifest only if a supporting file is needed. Load at most two candidate skills.
```
Direct loading:
```text
@@ -89,7 +72,7 @@ A repo-level instruction should name the native retrieval order and context budg
When a task matches a personal-mcp skill:
1. Prefer an already attached native skill resource.
2. Otherwise use `list_resources` and select one `skill://<name>/SKILL.md` resource by description.
2. Otherwise browse MCP resources and select one `skill://<name>/SKILL.md` resource by description.
3. Read `_manifest` only when supporting material is needed.
4. Load at most two candidate main files and only the relevant supporting paths.
5. Reconcile guidance with the current repository before editing.
@@ -107,7 +90,6 @@ Prompt modules remain separate from skills. When the client supports MCP prompt
2. Use `MCP: Browse Resources` to confirm native skill resources exist.
3. Restart the MCP server after changing skill files because production uses `reload=False`.
4. Reload the VS Code window if the server is healthy but the resource picker remains stale.
5. In tool-only sessions, verify `list_resources` and `read_resource` are visible.
## Further Reading