
Command Skill Name Conflation
- Updated November 3, 2025
- stbenjam/claude-code-bug-reproducers
command-skill-name-conflation is an agent skill that helps Claude Code plugin authors avoid overlapping command and skill names that cause wrong invocations.
About
command-skill-name-conflation is a narrowly scoped agent skill from the claude-code-bug-reproducers project aimed at developers who author Claude Code plugins and hit confusing overlaps between command names and skill names. The published description is still a TODO, so treat Prism tags as orientation: use it when reproducing or preventing registration bugs where a slash command and a skill slug look alike and the agent picks the wrong entry point. It belongs in Build agent-tooling alongside other meta skills for plugin hygiene. Confidence is moderate because documentation is incomplete—open the plugin source and any repro steps in the parent repo before production use. Best for maintainers extending Claude Code; not for end users shipping product features unrelated to plugin structure.
- Targets command-vs-skill naming collisions in Claude Code plugins
- Pairs with claude-code-bug-reproducers regression scenarios
- Helps plugin authors separate user-facing commands from skill identifiers
- Reduces mistaken invocations when agents parse overlapping names
- Stub skill—verify SKILL.md in repo before relying on full procedure
Command Skill Name Conflation by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add stbenjam/claude-code-bug-reproducers/plugin install command-skill-name-conflation@claude-code-bug-reproducersAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Last updated | November 3, 2025 |
|---|---|
| Repository | stbenjam/claude-code-bug-reproducers ↗ |
What it does
Avoid Claude Code plugin bugs where command names and skill names collide, so agents invoke the wrong capability or fail to register tools.
Who is it for?
Plugin authors debugging Claude Code registration issues in the bug-reproducers repo or similar custom plugins.
Skip if: Skip if you only consume third-party skills and never define commands or SKILL.md entries yourself.
When should I use this skill?
Authoring or debugging Claude Code plugins where command names and skill names may be conflated (description TODO in upstream—confirm triggers in repo).
What you get
You separate command and skill naming conventions so reproducers pass and agents resolve the intended plugin capability reliably.
- Distinct command vs skill naming scheme
- Reproducer notes for collision cases
Files
TODO: Add description
command-skill-name-conflation
Source: ./plugins/command-skill-name-conflation
{ "name": "command-skill-name-conflation", "source": "./plugins/command-skill-name-conflation", "description": "TODO: Add description" }
Related skills
How it compares
Plugin naming guardrail—not a general code review or security audit skill.
FAQ
Who is command-skill-name-conflation for?
It is for developers maintaining Claude Code plugins who need to disambiguate commands from skill names when tests or sessions misfire.
When should I use command-skill-name-conflation?
Use it during Build agent-tooling while authoring or fixing plugins when slash commands and skill identifiers collide; skip if your plugin uses distinct namespaces already.
Is command-skill-name-conflation safe to install?
The skill metadata is incomplete; review plugin source and the Security Audits panel on this Prism page before enabling in sensitive repos.