Plugin-namespaced slash commands (plugin:skill) feel cluttered in the picker/autocomplete

Status Open
Maintainer reply None cached
Activity 0 comments · opened Aug 13, 2026

Description

When a plugin ships multiple skills (e.g. a plugin with both email-helper and communication-specialist), each one shows up in the slash command list/autocomplete as /plugin-name:skill-name — e.g. /support-email-helper:email-helper. This is presumably to avoid name collisions across plugins, but it makes the picker feel noisy/unpolished, especially for plugins that bundle several related skills under one package.

Suggestion

A couple of options that would improve the feel without giving up collision safety:

  • Only show the plugin:skill qualified form when there's an actual name collision with another installed skill; otherwise show the short name in the picker/autocomplete.
  • Alternatively, allow a plugin to declare a "primary" skill that gets the unqualified short name, with the rest still addressable via the qualified form.

Additional context

Unqualified invocation (/email-helper) does appear to resolve fine when there's no collision — this is purely about how it's displayed in the command list/autocomplete, which currently always shows the fully-qualified form for any skill coming from a multi-skill plugin.

View original on GitHub ↗