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

[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!

[github-actions]

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

• [FEATURE]: add "/plugins" commands to discover Plugins, MCPs, and Skills (like Claude Code) #7716: add "/plugins" commands to discover Plugins, MCPs, and Skills (like Claude Code) - Related to skill discovery and marketplace
• [FEATURE]: display loaded skills in status page and sidebar #7533: display loaded skills in status page and sidebar - Related to skill visibility
• [FEATURE]: Add option to call sub-agents like CC and also being able to call skills #7457: Add option to call sub-agents like CC and also being able to call skills - Related to calling/invoking skills
• [FEATURE]: Plugin Hook for Registering Additional Config Directories #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.

[ChangeHow]

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.

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

[ChangeHow]

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

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