Manage Codex Skills

Treat skills-menu.json as the registry source and SKILLS_MENU.md as generated output.

Route a task

1. Scan every menu row by skill name, trigger, and output.
2. For each distinct task or subrequest, shortlist at most three relevant skills.
3. Read only the complete SKILL.md files for the shortlist.
4. State the order when multiple skills are complementary.
5. Continue without a skill when there is no good match.
6. Do not bulk-load all skills or route by category name alone.

Organize a library

1. Inventory skill names, descriptions, paths, categories, sources, and statuses read-only.
2. Detect missing registrations, duplicate names, invalid frontmatter, and path conflicts.
3. Propose a category for each unclassified skill with a short reason and confidence. This proposal is read-only and is not a persisted classification.
4. Show exact directory creations and optional relocations.
5. Let the user approve all, some, or none. An unmanaged skill stays in place and remains usable.
6. Apply only approved changes. Recording a category, rebuilding a user menu, or moving a skill is a write. Then validate the resulting menu.

Run scripts/rebuild_skills_menu.py to generate the menu. Run scripts/validate_skills_menu.py before reporting completion.

Passing format validation does not prove a skill is effective. Use draft before representative testing, tested after one successful realistic use, and stable only after repeated successful use.