Add skill organization: categories, hierarchy, enable/disable, and profiles

What variant of Codex are you using?

Codex App

What feature would you like to see?

Codex currently exposes installed skills in a flat namespace. Large skill collections often contain parent skills, child skills, related series, and orchestration skills, but those relationships are lost after installation. Once dozens or hundreds of skills are installed, the list becomes difficult to manage and overlapping descriptions can create noisy or ambiguous activation behavior.

Please add first-class skill organization and lifecycle management:

• Categories and user-defined tags, such as Research, Documents, Coding, and Bioinformatics.
• Parent/child relationships for skill packs, subskills, and dependencies.
• Enable, disable, and archive controls without deleting skill files.
• Global, project, and temporary/session scopes.
• Switchable skill profiles, for example Daily, Research, and Writing.
• Source, author, version, update status, and an official/verified badge.
• Detection of duplicate names, overlapping trigger descriptions, missing dependencies, and conflicting skills.
• A searchable and filterable skill management UI in the Codex App.
• CLI commands such as codex skills list, codex skills enable, codex skills disable, and codex skills profile.
• Only enabled skills should participate in the active skill index and trigger selection.

Additional information

This is not only a presentation problem. Users should be able to keep a complete skill library while allowing only a small active subset to participate in routing and context loading.

In a real cleanup case, a global installation expanded to roughly 160 Codex skills. Many were useful, but they represented related series or subskills in a flat list. Without classification or enable/disable support, the practical choices were either keeping an unmanageable active list or deleting useful skills.

A safe migration path would preserve the existing filesystem format while adding optional metadata for category, parent, dependencies, and profiles. Skills without the new metadata could remain uncategorized and enabled by default.