Feature request: let skills be organized under slash-path categories

What variant of Codex are you using?

app

What feature would you like to see?

Feature request: let skills be organized under slash-path categories

Problem

I have a lot of Codex skills installed now, and the flat skill list is getting hard to use.

Some skills are things I use every day, so I want them to stay easy to invoke at the top level:

/standup-summary
/quick-review

But many others are more specialized. I do not want all of them competing in one flat namespace. I would like to organize those under categories:

/docs/export-notes
/review/security
/review/performance
/deploy/release-checklist

Right now, skill names are basically flat. That works when there are only a few skills, but it does not scale well once a user has personal skills, repo-local skills, team skills, and plugin skills installed at the same time.

Requested behavior

Please support hierarchical skill aliases in the slash picker and invocation flow.

For example, users should be able to invoke skills like this:

/quick-review
/docs/export-notes
/review/security
/review/performance

The slash picker should also make these easier to find. Typing /docs or /docs/ should narrow the list to skills in that category.

Why this matters

This is mostly about day-to-day usability.

When the skill list is flat, I often forget the exact skill name or cannot quickly find the one I need. Categorizing skills would make the system easier to navigate without forcing every skill name to become long and awkward.

It would also reduce naming collisions. For example, security might be too generic as a top-level skill name, but /review/security is clear.

Possible design

One option is to keep the current skill name as the canonical identifier, and add optional aliases:

---
name: export-notes
description: Export project notes to Markdown.
aliases:
  - docs/export-notes
---

Another option is a category field:

---
name: export-notes
description: Export project notes to Markdown.
category: docs
---

The important part is that /docs/export-notes should map deterministically to that skill.

Existing flat skill names should keep working for backward compatibility.

Related issues

This is related to existing requests around skill discovery and slash invocation, but it is a bit different:

• #28754 asks for repo-local skills to be invocable from the / surface.
• #20778 asks for installed skills to appear in slash autocomplete.
• #19672 discusses nested skill discovery.
• #22275 points out problems caused by recursive nested SKILL.md discovery.

This request is specifically about user-facing organization: letting users manage many skills through category-style slash aliases such as /docs/export-notes.

Non-goals

This does not need to change automatic skill activation.

The main goal is explicit invocation and discoverability:

• easier navigation in the slash picker
• category-based organization
• fewer naming conflicts
• less pressure to keep every skill in one flat namespace

Additional information

_No response_