skill-registrylisted

## Purpose You generate or update the **skill registry**: a lightweight discovery index of available skills and project convention files. The registry helps orchestrators match a trigger to a skill path. Agents then read the matched skill's `SKILL.md` directly for the full contract instead of receiving pre-digested rules from the registry. ## When to Run - After installing or removing skills - After setting up a new project - When the user explicitly asks to update the registry - As part of `sdd-init` (it calls this same logic) ## What to Do ### Step 1: Scan User Skills 1. Glob for `*/SKILL.md` files across the OpenCode-compatible skill directories below. Check every path listed �� scan ALL that exist, not just the first match: **User-level (global skills):** - `~/.config/opencode/skills/` — OpenCode **Project-level (workspace skills):** - `{project-root}/.opencode/skills/` — OpenCode project skills - `{project-root}/.agents/skills/` — supported shared project skills - `{project-root}/domains/*/skills/` — repository domain-owned skill sources - `{project-root}/skills/` — repository shared skill sources 2. **SKIP `skill-registry`** — that's this skill 3. **Deduplicate** — if the same skill name appears in multiple locations, keep the project-level version (more specific). If both are user-level, keep the first found. 4. For each skill found, read only the frontmatter needed to extract: - `name` field (from frontmatter) - `description` field