Skill Delete

When a skill must be retired — superseded, dissolved into other skills, or demoted to a knowledge doc. Deleting a skill is a graph operation: its :ID: leaves the org-roam graph, and any document still linking it breaks the site build. Also invoked by compass-skill-review on its deletion list and by compass-skill-add when a new skill subsumes an old one.

1. Find every incoming link first. The skill's :ID: is in its SKILL.org; search the whole repository, not just living docs — archived sprint documents break the site build too:

   git grep -l "<skill-uuid>"
   ./projects/ores.compass/compass.sh show <skill-uuid>
   

2. Re-point or downgrade each link. Pick per referrer:
   • a successor skill or knowledge doc exists → re-point the id-link there, keeping the label;
   • no successor → downgrade [[id:...][name]] to plain name text. Never leave a dead id-link.
3. Remove the source: git rm -r doc/llm/skills/<name>/.

4. Regenerate the catalogue:

   python3 build/scripts/generate_skills_catalogue.py
   

5. Rebuild the bundle and purge the deployed copy — deployment does not remove stale directories:

   ./projects/ores.compass/compass.sh build --direct skills
   rm -rf .claude/skills/<name>
   

6. Verify the graph: publish the changed pages and confirm no broken id-links:

   ./projects/ores.compass/compass.sh site page
   

• How do I deploy the skills? — rebuild the bundle.

• Skill naming conventions — the policy; deletions follow from its structural rules (roles dissolved, reference-only demoted).
• Skills catalogue — the inventory, which carries the current set and nothing else. What a skill used to be called is in git.