[FEATURE]:desktop: slash command list does not show skills #50638

Activity

1. github-actions

   assigned

   Hona

   on Sep 22, 2026
2. github-actions commented on Sep 22, 2026

   

   github-actionsBot

   on Sep 22, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • Desktop skill slash commands should match TUI defaults #48022: Desktop skill slash commands should match TUI defaults — reports the same gap where Desktop hides skills from the / autocomplete list unless slash: true is set, while the TUI shows them by default.
3. Echo3clipse commented on Sep 25, 2026

   

   Echo3clipse

   on Sep 25, 2026

   Last edited by Echo3clipse

   More actions

   I do not consider this a duplicate of #48022, as that issue is about a difference in handling between the TUI and the desktop app, but both TUI and desktop app (v2.0.16) show the same slash-menu behavior for skills.

   I wouldn't consider this request here a feature, but a bug.
   The v2-documentation clearly states that the skills are only hidden from the slash-menu when the yaml front matter contains slash: false
   See: https://opencode.ai/v2/docs/skills/#frontmatter

   slash Set to false to hide the skill from interactive command catalogs

   I interpret this as: If slash: is not set at all or is set to true, then the skill should show up.

   Either way, even if the skill front matter is set to slash: true as @cgyqu described, then those skills do not show up in the slash-menu, neither for desktop nor TUI (v2.0.16). It was working fine for me in opencode v1.
4. michaelmell commented on Sep 25, 2026

   

   michaelmell

   on Sep 25, 2026

   More actions

   I just ran into the same issue. (I am trying to migrate from claude-code.)

   Adding slash: true to skill frontmatter does not make the skill show up as slash command. As should be expected reading this.

   I worked around this by creating a command entry for each skill like so, but that seems hacky. E.g. in .opencode/command/commit.md:

   ---
   description: Create git commit(s) using Conventional Commits.
   ---
   
   Load the `commit` skill using the skill tool and follow its instructions exactly.
   
   $ARGUMENTS
5. psamsoon commented on Oct 7, 2026

   

   psamsoon

   on Oct 7, 2026

   More actions

   Still reproducible in 2.0.24 (Desktop, macOS) — with service-level evidence

   Dug into this on 2.0.24 (Desktop sidecar CLI, latest channel), macOS 25.6.0 arm64 and confirmed it's a registry split, not a config/loading issue:

   • GET /api/skill?location[directory]=… → 16 skills registered, all with descriptions (better-ui, better-interface, break, …).
   • GET /api/command?location[directory]=… → only init, review, and 2 notion:* entries. Zero skill-sourced entries.
   • In the v2.0.24 source, packages/schema/src/skill.ts has no slash field, and packages/opencode/src/command/index.ts never merges skills into the command registry — so slash: true frontmatter (suggested in the comments above) cannot work in this version, and the / list — built exclusively from the command list — can never contain skills.
   • The TUI-only prompt.skills picker (/skills) isn't available in the Desktop chat either (see desktop: /skills skill picker missing — works only in CLI TUI #50664), so / ends up being the only discovery surface, and it shows nothing skill-related. Result: users conclude their skills failed to install.

   Suggested directions

   1. Surface registered skills in the / autocomplete, grouped/badged as skills, and/or
   2. Give /skills a real description in the default Desktop command list ("browse N installed skills") so the picker is discoverable.

   Workaround that works today: drop one thin command file per skill into ~/.config/opencode/commands/<skill-id>.md:

   ---
   description: "<skill description>"
   ---
   
   Load the `<skill-id>` skill with the skill tool and apply it to this request.
   
   $ARGUMENTS

   Commands are auto-discovered and appear in / immediately; running one makes the model load the exact skill by ID. All 13 of my skills are now reachable as /better-ui, /interface-review, etc. without touching the packaged app.
6. opencodejr commented on Oct 28, 2026

   

   opencodejrBot

   on Oct 28, 2026

   Contributor

   More actions

   Thanks for the detailed request!

   In OpenCode v2, skills deliberately aren't / commands. You load one yourself by mentioning it as @skill-id in the prompt, and the Desktop composer suggests skills when you type @. The slash frontmatter field you saw in the docs was removed from v2 (see #52752), so slash: true has no effect.

   I've noted this as a feature request to also list skills in the / command list. Maintainers will consider it. Until then, you can use @skill-id, or keep the command-file wrappers you already set up.

   Related issues:

   • skills: slash frontmatter field has no effect; skills never appear in the command registry #51753: the slash field had no effect; closed by the docs change in docs: remove skill slash frontmatter from v2 docs #52752
   • skills: documented slash frontmatter is not implemented in v2.0.18 #51427: the same missing slash support, reported on 2.0.18