implemented steps 1-5

docs/skills/copilot-customization/SKILL.md

@@ -2,6 +2,31 @@
 name: copilot-customization
 description: 'Plan, create, review, and debug GitHub Copilot and VS Code agent customizations, including instructions, prompt files, skills, custom agents, hooks, MCP servers, and repo-specific personal-mcp skill integration.'
 argument-hint: 'What Copilot behavior are you customizing, and should it be workspace-scoped, personal, or exposed as an MCP skill resource?'
+x-personal-mcp:
+  id: copilot-customization
+  version: 1.0.0
+  tags:
+    - copilot
+    - vscode
+    - customization
+    - instructions
+    - prompts
+    - agent-skills
+    - custom-agents
+    - hooks
+    - mcp
+    - personal-mcp
+    - skills
+  capabilities:
+    - resource://skills/copilot-customization/document
+  depends_on:
+    - new-skill
+    - zensical-docs
+  references:
+    vscode-customization:
+      path: references/vscode-customization.md
+      mime_type: text/markdown
+      title: VS Code Customization
 ---
 
 # Copilot Customization
@@ -51,15 +76,14 @@ Use [VS Code customization references](./references/vscode-customization.md) for
 When adding a new skill to this `personal-mcp` repo, follow the resource-first pattern:
 
 1. Search the catalog for `new skill` and load `resource://skills/new-skill/document`.
-2. Create authored docs under `docs/skills/<slug>/SKILL.md`, with optional one-level `references/` files.
-3. Choose consistent names: docs slug and resource id use kebab-case; Python namespace uses snake_case.
-4. Create `src/personal_mcp/skills/<python_namespace>/` with `__init__.py`, `server.py`, and `metadata.yaml`.
-5. Expose only `resource://skills/<skill-id>/document` from the per-skill server.
-6. Put discovery metadata in `metadata.yaml`, including `id`, `name`, `version`, `description`, `tags`, `capabilities`, and `depends_on`.
-7. Mount the skill server in `src/personal_mcp/mcp.py` using the Python namespace.
-8. Validate with the document loader and `uv run zensical build`.
+2. Create authored docs under `docs/skills/<skill-id>/SKILL.md`, with optional nested `references/` markdown files.
+3. Keep `skill-id` stable and consistent across directory name, `name`, and `x-personal-mcp.id`.
+4. Put discovery metadata in `SKILL.md` frontmatter under `x-personal-mcp`.
+5. Declare `resource://skills/<skill-id>/document` in `x-personal-mcp.capabilities`.
+6. Declare references in `x-personal-mcp.references` as `ref-id -> references/<file>.md` mappings.
+7. Validate with the registry loader and `uv run zensical build`.
 
-Keep per-skill servers resource-only. Catalog-level discovery is the only place for thin fallback discovery tools.
+Keep runtime implementation registry-driven in `src/personal_mcp/mcp.py`; do not add per-skill Python server modules.
 
 ## Quality Checks