Repository navigation
[FEATURE]: allow selecting multiple skills from /skills #32954
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
I would like /skills in the TUI to support selecting multiple skills for one prompt.
Current behavior:
/skillsopens the skills selector.- Selecting a skill inserts
/<skill>into the prompt. - Only one skill can be selected at a time.
- If I want to combine multiple skills, I have to try invoking
/skillsagain, which is awkward and does not work well inside the same prompt.
Requested behavior:
/skillsopens a selector that allows selecting multiple skills.- The user can toggle skills on/off, for example with space.
- Enter applies the selected skills to the current prompt.
- The prompt UI could show something like
2 skills selected.
Use case:
Some tasks benefit from combining multiple skills, for example:
- a repo-specific skill +
review effect+investigatebaseline-ui+design-review
Expected behavior:
- I can select multiple skills from one
/skillsdialog. - The selected skills are applied together to the next request.
Considerations:
- The UI should make selected skills visible before submit.
- Combining skills may need safeguards for context/token usage.
- If selected skills conflict, OpenCode may need a clear ordering or conflict policy.
Would you accept multi-skill selection for /skills as a feature proposal?
Reacted by mex7xx, Esai, Willian Alves, Maxim Bovtunov, Ramiro Somavilla, Oleksii Poberezhnyi, Tejush, RayArnold, Hazem Mohamed and Alberto Ortiz
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Jun 19, 2026
This issue might be a duplicate of existing issues. Please check:
X6TXY commentedon Jun 23, 2026
Could you check it out? @simonklee
WodenJay commentedon Jul 5, 2026
how about use
$SKILL_NAMEor/SKILL_NAMEto load skills likecodexandclaude code?DominikWidomski commentedon Aug 6, 2026
This is possibly a separate feature request but might as well tack it on:
Would it make sense for user invoked skills to be invoked as a tool in the same way that the agent invokes a tool?
From what I can tell, and I might be missing something, if an agent reasons and chooses to invoke a skill it calls the
skill_contenttool, which is then nicely traceable in the session. However if a user references it it copy pastes it into the prompt so it's not programatically obvious that this was a skill invocation. It might be nice to be able to do so.Thoughts?
tejush1998 commentedon Aug 12, 2026
@kitlangton @thdxr @MrMushrooooom @rekram1-node could you look into this? Seems like a pretty basic feature we should have. Or is this being addressed in v2?
X6TXY commentedon Sep 25, 2026
guys, just use opencode2 this problem solved there. type @ and choose your skill(any amount of it) anywhere of your prompt