Skill name collision across plugins: fully qualified name resolves to wrong plugin

Description

When two installed plugins define skills with the same name (e.g., both telegram and signal plugins have a skill named configure), typing the fully qualified /signal:configure auto-swaps to /telegram:configure.

Steps to reproduce

1. Install two plugins that each have a skill with the same name (e.g., configure)

• Plugin A: telegram@claude-plugins-official with skills/configure/SKILL.md
• Plugin B: signal@BrendanMartin-claude-plugins with skills/configure/SKILL.md

1. Enable both plugins in settings.json → enabledPlugins
2. Start Claude Code with --dangerously-load-development-channels plugin:signal@BrendanMartin-claude-plugins
3. Type /signal:configure in the prompt

Expected behavior

/signal:configure should invoke the configure skill from the signal plugin.

Actual behavior

• Typing /signal in autocomplete correctly shows: /configure (signal) Set up the Signal channel...
• But selecting it or typing /signal:configure manually auto-swaps to /telegram:configure
• The signal plugin's skill is never reachable

Workaround

Rename conflicting skills to unique names (e.g., setup instead of configure, allow instead of access).

Environment

• Claude Code CLI on Windows 11
• Claude Opus 4.6