Plugin skills show short name in slash palette instead of documented namespaced form (/plugin:skill)

Open 💬 1 comment Opened Jul 8, 2026 by alessandrovarela

Environment

  • Claude Code 2.1.204, macOS (darwin 25.4.0), terminal TUI

Description

Skills shipped by a plugin (plugin.json with "skills": "./core/skills") appear in the slash-command palette by their short name (e.g. /setup, /spec), with the plugin name shown only inside the description text ((my-plugin) ...).

The documentation states plugin skills are always namespaced:

  • plugins.md — "Plugin skills are always namespaced (like /my-first-plugin:hello) to prevent conflicts when multiple plugins have skills with the same name."
  • skills.md, table "How a skill gets its command name" — my-plugin/skills/review/SKILL.md → /my-plugin:review

Expected

Palette lists plugin skills with the namespaced command name in the name column: /my-plugin:review.

Actual

Palette lists them as /review, plugin provenance only in the description column. Typing the full namespaced form (/my-plugin:review) does execute the right skill, so execution disambiguation works — the issue is display/discoverability only.

Impact

  1. Discoverability: users don't learn the namespaced form exists; typing /my-plugin: as a filter is the natural way to browse one plugin's commands.
  2. Collision confusion: a plugin skill named like a built-in (e.g. init) shows two visually identical entries whose only differentiator is buried in the description. We renamed our skills (initsetup) to work around it.

Repro

  1. Create a plugin with .claude-plugin/plugin.json ("name": "my-plugin") and skills/hello/SKILL.md.
  2. Install it from a local marketplace; /reload-plugins.
  3. Type / — the entry shows as /hello, not /my-plugin:hello.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗