[Question] Are there plans for AI skills support in ACP?

[alewkinr]

I'm wondering whether there are plans to support the skills concept as part of the ACP protocol.

I think that, if skills were supported at the ACP level, IDEs could present a more structured menu of capabilities and improve the user experience. I know I can probably work around this by mapping skills in AGENTS.md, but it would be nice to reference them more directly from the AI panel.

[alexghergh]

+1 for this.

The capability is already supported by ACP through available_commands_update, but the current codex-acp code doesn't support it.

The question is how to expose these correctly via ACP. For example, Claude Code already supports skills via / triggers (and the claude-agent-acp correctly uses that), but Codex only has /skills as a CLI command, which opens the skills menu. This means that duplicate skill names will possibly conflict with other Codex-native / commands, making it a bit trickier.

I'm happy to submit an initial PR for this without skill name deduplication (possibly with /skills:foo as a command trigger), just as an initial RFC, if there are no other plans related to skills implementation.

Also CC @benbrandt

[CsBigDataHub]

Now $ to load a skill in codex

[permanar]

Bump this up.

Cuz I've been wondering if this is still on the future plan?
Because right now seems like Zed still didn't acknowledge my existing skills while I'm using Codex inside.

[priyashpatil]

I found that just doing skill prefix with $ (the codex way) codex automatically figures out the skills. It works most of the time.

[maximilianigl]

I found that just doing skill prefix with $ (the codex way) codex automatically figures out the skills. It works most of the time.

If it works only most of the time, than that's probably just the normal "skill detection" based on context. It would be good to have a way to get a list of skill available (like e.g. when using $ in the codex cli).

[daniel-agentee]

Took a swing at this in #279 — opened a PR that exposes Codex skills as ACP slash commands.

Approach:

• Skills from SkillsManager::skills_for_cwd are advertised in AvailableCommandsUpdate alongside the builtins, refreshed on session load and on EventMsg::SkillsUpdateAvailable.
• Picking /code-review rewrites the leading text into $code-review ... and submits as a normal Op::UserInput, so Codex's detect_implicit_skill_invocation_for_command handles it the same way the TUI's $ picker does. No new Codex-side surface needed.
• Went with flat /name rather than /skills:name after some back-and-forth — matches what claude-code-acp does and the builtin namespace is small enough that collisions can be handled by dropping the skill (with a warning).

Known gap: plugin-supplied skill roots aren't threaded through yet (effective_skill_roots = vec![]), so plugin-distributed skills won't appear in the menu yet. Follow-up.

@alexghergh — saw your offer above; happy to defer or collaborate if you'd rather drive this. @benbrandt — would appreciate a sanity check on the naming choice and whether the plugin-roots gap should land in this PR or a follow-up.