anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Add /skills command to list and quick-invoke skills #4768

New Issue
Open
opened 2026-02-16 17:45:21 -05:00 by yindo · 15 comments
yindo commented 2026-02-16 17:45:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @nguyenngothuong on GitHub (Jan 11, 2026).

Originally assigned to: @rekram1-node on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Related but different from #7716 (marketplace discovery) and #7533 (display in sidebar).

Problem

Currently, there's no quick way to:

  1. List available skills from the TUI prompt
  2. Invoke a specific skill directly via slash command

Users must either:

  • Know skill names beforehand and hope the LLM picks them up
  • Run opencode debug skill in terminal (not discoverable)

Proposed Solution

1. /skills command - List all available skills

/skills

Shows a searchable list of loaded skills with:

  • Skill name
  • Short description
  • Source (global/project)

2. /skill:<name> - Quick invoke syntax

/skill:code-review
/skill:meeting-notes

When typing /skill:, autocomplete shows available skills (similar to @ for files).

This would work like Claude Code's new skill invocation feature.

Use Cases

  • Discoverability: New users can explore what skills are available
  • Quick access: Power users can invoke skills without typing full prompts
  • Consistency: Matches existing patterns (/models, /themes, /sessions)

Suggested Implementation

  1. Add /skills to command list (similar to /models)
  2. Register skill: as autocomplete trigger (like @ for files)
  3. When selected, inject skill name into system prompt or trigger skill loading

Environment

  • OpenCode version: v1.0.x
  • This is a feature request for TUI

Happy to contribute a PR if the maintainers agree with this direction!

Originally created by @nguyenngothuong on GitHub (Jan 11, 2026). Originally assigned to: @rekram1-node on GitHub. ## Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. Related but different from #7716 (marketplace discovery) and #7533 (display in sidebar). ## Problem Currently, there's no quick way to: 1. **List available skills** from the TUI prompt 2. **Invoke a specific skill** directly via slash command Users must either: - Know skill names beforehand and hope the LLM picks them up - Run `opencode debug skill` in terminal (not discoverable) ## Proposed Solution ### 1. `/skills` command - List all available skills ``` /skills ``` Shows a searchable list of loaded skills with: - Skill name - Short description - Source (global/project) ### 2. `/skill:<name>` - Quick invoke syntax ``` /skill:code-review /skill:meeting-notes ``` When typing `/skill:`, autocomplete shows available skills (similar to `@` for files). This would work like Claude Code's new skill invocation feature. ## Use Cases - **Discoverability**: New users can explore what skills are available - **Quick access**: Power users can invoke skills without typing full prompts - **Consistency**: Matches existing patterns (`/models`, `/themes`, `/sessions`) ## Suggested Implementation 1. Add `/skills` to command list (similar to `/models`) 2. Register `skill:` as autocomplete trigger (like `@` for files) 3. When selected, inject skill name into system prompt or trigger skill loading ## Environment - OpenCode version: v1.0.x - This is a feature request for TUI --- Happy to contribute a PR if the maintainers agree with this direction!
yindo added the opentui label 2026-02-16 17:45:21 -05:00
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Jan 11, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #7716: add "/plugins" commands to discover Plugins, MCPs, and Skills (like Claude Code) - Related to skill discovery and marketplace
  • #7533: display loaded skills in status page and sidebar - Related to skill visibility
  • #7457: Add option to call sub-agents like CC and also being able to call skills - Related to calling/invoking skills
  • #6347: Plugin Hook for Registering Additional Config Directories - Related to skill/command discovery configuration

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 11, 2026): This issue might be a duplicate of existing issues. Please check: - #7716: add "/plugins" commands to discover Plugins, MCPs, and Skills (like Claude Code) - Related to skill discovery and marketplace - #7533: display loaded skills in status page and sidebar - Related to skill visibility - #7457: Add option to call sub-agents like CC and also being able to call skills - Related to calling/invoking skills - #6347: Plugin Hook for Registering Additional Config Directories - Related to skill/command discovery configuration Feel free to ignore if none of these address your specific case.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@ChangeHow commented on GitHub (Jan 12, 2026):

need it too！I'm using GLM and it always forget to load and run skill automatically. So that I need to add a command that add "once finish, check if there is any skill you need to run" to the end of prompt.

@ChangeHow commented on GitHub (Jan 12, 2026): need it too！I'm using GLM and it always forget to load and run skill automatically. So that I need to add a command that add "once finish, check if there is any skill you need to run" to the end of prompt.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@polyrand commented on GitHub (Jan 15, 2026):

I also think this would be a very welcome change. Although I would prefer the approach of Claude Code / Codex where you can directly invoke a skill without having to type /skill: first.

@polyrand commented on GitHub (Jan 15, 2026): I also think this would be a very welcome change. Although I would prefer the approach of Claude Code / Codex where you can directly invoke a skill without having to type `/skill:` first.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@ChangeHow commented on GitHub (Jan 15, 2026):

I also think this would be a very welcome change. Although I would prefer the approach of Claude Code / Codex where you can directly invoke a skill without having to type /skill: first.

In my test, only Claude opus and codex models can invoke skill automatically even user used too much context. I'm using GLM4.7 for the daily easy(or medium) works, and it won't to invoke skill automatically if I don't prompt it.

So I added a custom command /with-skill to prompt it, but I sometimes forget to run this command so that I have to use /undo and re-prompt to attach my command. 😇

@ChangeHow commented on GitHub (Jan 15, 2026): > I also think this would be a very welcome change. Although I would prefer the approach of Claude Code / Codex where you can directly invoke a skill without having to type `/skill:` first. In my test, only Claude opus and codex models can invoke skill automatically even user used too much context. I'm using GLM4.7 for the daily easy(or medium) works, and it won't to invoke skill automatically if I don't prompt it. So I added a custom command /with-skill to prompt it, but I sometimes forget to run this command so that I have to use /undo and re-prompt to attach my command. 😇
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@frytyler commented on GitHub (Jan 15, 2026):

+1 for skill invocation, but I'd advocate for following the Agent Skills open standard rather than introducing a new /skill:<name> syntax.

The standard (created by Anthropic) allows direct /<skillName> invocation - same as Claude Code and Cursor. This gives us:

  • Interoperability - Skills work the same across Claude Code, Cursor, OpenCode, Gemini CLI, etc.
  • Simpler UX - /<skillName> instead of /skill:<skillName>
  • Ecosystem alignment - OpenCode already supports ~/.claude/skills/ paths for compatibility

Cursor's implementation: https://cursor.com/docs/context/skills

"Skills can also be manually invoked by typing / in Agent chat and searching for the skill name"

Would love to see OpenCode follow this pattern rather than diverging with a different syntax.

@frytyler commented on GitHub (Jan 15, 2026): +1 for skill invocation, but I'd advocate for following the [Agent Skills open standard](https://agentskills.io/home) rather than introducing a new `/skill:<name>` syntax. The standard (created by Anthropic) allows direct `/<skillName>` invocation - same as Claude Code and Cursor. This gives us: - **Interoperability** - Skills work the same across Claude Code, Cursor, OpenCode, Gemini CLI, etc. - **Simpler UX** - `/<skillName>` instead of `/skill:<skillName>` - **Ecosystem alignment** - OpenCode already supports `~/.claude/skills/` paths for compatibility Cursor's implementation: https://cursor.com/docs/context/skills > "Skills can also be manually invoked by typing / in Agent chat and searching for the skill name" Would love to see OpenCode follow this pattern rather than diverging with a different syntax.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@tanggit123 commented on GitHub (Jan 23, 2026):

+1 , I am also expecting this feature. this is very important for user experience. Claude code have this , it is working like a charm. plz add this feature.

@tanggit123 commented on GitHub (Jan 23, 2026): +1 , I am also expecting this feature. this is very important for user experience. Claude code have this , it is working like a charm. plz add this feature.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@tanggit123 commented on GitHub (Jan 23, 2026):

plz add autocomplete for skill names

@tanggit123 commented on GitHub (Jan 23, 2026): plz add autocomplete for skill names
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@InCerryGit commented on GitHub (Jan 27, 2026):

+1，same request.

@InCerryGit commented on GitHub (Jan 27, 2026): +1，same request.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@luosky commented on GitHub (Jan 28, 2026):

+1. This would be very helpful.

@luosky commented on GitHub (Jan 28, 2026): +1. This would be very helpful.
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@tanggit123 commented on GitHub (Jan 28, 2026):

it is a very important feature that keep me in claude code; auto is good ,
but still have chance to fail to call a certain skill sometimes , so , it
is always helpful to call a skill manually. I can see that claude code is
tend to combine skill and slash command as one.

On Wed, Jan 28, 2026 at 3:45 PM Luosky @.***> wrote:

luosky left a comment (anomalyco/opencode#7846)
https://github.com/anomalyco/opencode/issues/7846#issuecomment-3809567394

+1. This would be very helpful.

—
Reply to this email directly, view it on GitHub
https://github.com/anomalyco/opencode/issues/7846#issuecomment-3809567394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BG5IQOUBVAAUEDNX672RX534JBSLLAVCNFSM6AAAAACRLFFC5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBZGU3DOMZZGQ
.
You are receiving this because you commented.Message ID:
@.***>

@tanggit123 commented on GitHub (Jan 28, 2026): it is a very important feature that keep me in claude code; auto is good , but still have chance to fail to call a certain skill sometimes , so , it is always helpful to call a skill manually. I can see that claude code is tend to combine skill and slash command as one. On Wed, Jan 28, 2026 at 3:45 PM Luosky ***@***.***> wrote: > *luosky* left a comment (anomalyco/opencode#7846) > <https://github.com/anomalyco/opencode/issues/7846#issuecomment-3809567394> > > +1. This would be very helpful. > > — > Reply to this email directly, view it on GitHub > <https://github.com/anomalyco/opencode/issues/7846#issuecomment-3809567394>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/BG5IQOUBVAAUEDNX672RX534JBSLLAVCNFSM6AAAAACRLFFC5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBZGU3DOMZZGQ> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@oliviermilla commented on GitHub (Jan 29, 2026):

+1

@oliviermilla commented on GitHub (Jan 29, 2026): +1
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@mashedmonday commented on GitHub (Feb 3, 2026):

+1

@mashedmonday commented on GitHub (Feb 3, 2026): +1
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@jairbubbles commented on GitHub (Feb 3, 2026):

It was fixed in a recent version.

Image
@jairbubbles commented on GitHub (Feb 3, 2026): It was fixed in a recent version. <img width="1129" height="187" alt="Image" src="https://github.com/user-attachments/assets/3c8291bc-41bf-4fc1-ac31-dd3b6cb952f2" />
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@prometx11 commented on GitHub (Feb 6, 2026):

So this issue can be closed no?

@prometx11 commented on GitHub (Feb 6, 2026): So this issue can be closed no?
yindo commented 2026-02-16 17:45:22 -05:00
Author
Owner
Copy Link
Copy Source

@MichaelYochpaz commented on GitHub (Feb 15, 2026):

Skills do appear to be invokable from the TUI, but not from the Desktop / web app? The /skills command doesn't appear there.

Also, on the TUI, it appears like existing skills don't appear as commands for auto-completion with the proposed commands, they have to be fully typed, or added by running /skills first and then picking a skill.

@MichaelYochpaz commented on GitHub (Feb 15, 2026): Skills do appear to be invokable from the TUI, but not from the Desktop / web app? The `/skills` command doesn't appear there. Also, on the TUI, it appears like existing skills don't appear as commands for auto-completion with the proposed commands, they have to be fully typed, or added by running `/skills` first and then picking a skill.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label opentui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4768
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?