TUI: ctrl+a skill actions picker never opens in the /skills browser (blocks Publish to workspace from the TUI)

[anandgupta42]

Summary

In the /skills browser, ctrl+a (the "Skill actions" picker: Show / Edit / Test / Remove / Publish to workspace) never opens. Reproduced on v0.12.0 under tmux and under vhs (ttyd + headless Chromium), on macOS 25.5, with and without ALTIMATE_WORKSPACE=1.

Because the picker is the only TUI route to Publish to workspace (#1313), the pilot's "publish from the TUI" path is unreachable in practice; only altimate-code skill publish <name> works.

Steps

1. altimate-code in a project with at least two project skills under .opencode/skills/.
2. Type /skills + Enter. The Skills dialog opens with the search box focused and the first row highlighted.
3. Press Down (to move the highlight, so onMove records a current skill), then ctrl+a.

Expected: the Actions: <skill> picker opens.
Actual: nothing happens. The dialog stays as is. Enter on the row still works (inserts /<skill> into the prompt).

What I looked at

• The binding is registered as a keymap layer at plugin init: { key: "ctrl+a", cmd: "altimate.skill.actions" } (packages/opencode/src/plugin/tui/altimate/skill-ops.tsx around line 889), and showActions no-ops unless currentSkill is set (line ~829).
• The search TextInput has focus while the list is shown. My best guess is that the input consumes ctrl+a (readline "beginning of line" / select-all) before the keymap layer sees it, so the command never runs. Moving the highlight first did not change the outcome, so it is not only the currentSkill guard.
• ctrl+n (create) was not tested.

Suggested fix

Either handle ctrl+a inside the dialog while the input is focused and forward it to altimate.skill.actions, or add a visible "Actions" affordance that does not depend on a chord (for example a second Enter on an already-selected row, or a right-hand hint that opens the picker). The docs (docs/docs/configure/skills.md, TUI table) list ctrl+a as "Actions", so either the code or the docs need to move.

Context

Found while recording the workspace pilot demos (demos/workspace-pilot/README.md in the workspace_learning worktree has the setup). Happy to retest a fix under the same vhs tape.

[anandgupta42]

@sahrizvi assigning this to you. Repro is deterministic under vhs and tmux on v0.12.0; the tape demos/workspace-pilot/tapes/d3-team-playbook.tape (workspace_learning worktree) has the exact key sequence. Happy to retest once there is a build.

[sahrizvi]

Shipped in v0.12.2-beta.1 on the npm beta channel (npm i -g @altimateai/altimate-code@beta); latest is still 0.12.1. Release: https://github.com/AltimateAI/altimate-code/releases/tag/v0.12.2-beta.1

[anandgupta42]

Re-checked on 0.12.1 during the workspace release tests. Two observations that narrow this down:

• Enter on a skill row in the Altimate Skills browser opens the per-skill action menu (Show / Edit / Test / Remove / Publish to workspace), so the actions are reachable; this issue is about the ctrl+a shortcut specifically.
• In one vhs run, after filtering the list down to a single row, ctrl+a did open the action picker. In the earlier runs (unfiltered list, cursor on the first row) it never did. So it may be timing- or focus-dependent rather than dead, and worth a hands-on check of where focus sits when the list has more than one row.

[sahrizvi]

Released in v0.12.2 (latest): https://github.com/AltimateAI/altimate-code/releases/tag/v0.12.2