skill-registry

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: