Skip to content

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

Closed as not planned

Description

@nguyenngothuong

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!

Activity

  1. added
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on Jan 11, 2026
  2. github-actions commented on Jan 11, 2026

    @github-actions
    Contributor

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

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

  3. ChangeHow commented on Jan 12, 2026

    @ChangeHow
    Contributor

    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.

  4. polyrand commented on Jan 15, 2026

    @polyrand

    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.

  5. ChangeHow commented on Jan 15, 2026

    @ChangeHow
    Contributor

    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. 😇

  6. frytyler commented on Jan 16, 2026

    @frytyler

    +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.

  7. added a commit that references this issue on Jan 19, 2026
    953d151
  8. tanggit123 commented on Jan 23, 2026

    @tanggit123

    +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.

  9. tanggit123 commented on Jan 23, 2026

    @tanggit123

    plz add autocomplete for skill names

  10. InCerryGit commented on Jan 27, 2026

    @InCerryGit

    +1,same request.

  11. luosky commented on Jan 28, 2026

    @luosky

    +1. This would be very helpful.

  12. tanggit123 commented on Jan 28, 2026

    @tanggit123
  13. oliviermilla commented on Jan 29, 2026

    @oliviermilla

    +1

  14. mashedmonday commented on Feb 3, 2026

    @mashedmonday

    +1

  15. 6 remaining items

  16. added 2 commits that reference this issue on Mar 16, 2026
    441a925
  17. raine commented on Apr 4, 2026

    @raine

    Why doesn't tab autocomplete skills?

  18. gardnmi commented on Apr 23, 2026

    @gardnmi

    The OpenCode Agent in Zed gives you shortcuts.

    Image
  19. softwarecrafters-io commented on Apr 23, 2026

    @softwarecrafters-io

    +1

  20. gliptak commented on Apr 26, 2026

    @gliptak
  21. removed
    opentuiThis relates to changes in v1.0, now that opencode uses opentui
    on May 3, 2026
  22. cristiano-pacheco commented on May 16, 2026

    @cristiano-pacheco

    +1

  23. jjdubski commented on May 26, 2026

    @jjdubski

    @tanggit123 @InCerryGit @luosky @oliviermilla @mashedmonday @MichaelYochpaz @c8i-dev @bigcoder84 @ThomasTrepanier @softwarecrafters-io and others that are interested, please checkout my PR #29217 and support with a comment/reaction. thank you!

  24. DandyLyons commented on Jul 6, 2026

    @DandyLyons

    Is it just me or is the current implementation of /skills broken? When I type /skills it brings up a menu. Then I select a skill and it pastes /my-selected-skill into my prompt. Then when I send my prompt, it replaces /my-selected-skill with the entire contents of that SKILL.md file. But it never actually used the native Skill tool, and it doesn't seem to know that it read a skill, because later in my conversation it realizes that the skill is relevant, uses the Skill tool, and then loads the exact same skill all over again.

  25. tanggit123 commented on Jul 9, 2026

    @tanggit123
  26. imohuan commented on Jul 31, 2026

    @imohuan

    I think we could also add skills to the dropdown menu triggered by @, or use $ alone to trigger the skill dropdown.

  27. jjdubski commented on Jul 31, 2026

    @jjdubski

    I think we could also add skills to the dropdown menu triggered by @, or use $ alone to trigger the skill dropdown.

    Check out my PR #29217

  28. github-actions commented on Oct 1, 2026

    @github-actions
    Contributor

    To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions