Slash-Command Namespacing
Plugin-provided slash commands are always namespaced as /<plugin-name>:<skill-name>. There is no shorter form.
Why namespacing
Section titled “Why namespacing”Claude Code namespaces commands so two plugins can each ship a skill named review without colliding. The <plugin>:<skill> form makes the source explicit and the picker unambiguous. If a personal user-scope skill and a plugin skill share a name, the plugin form wins on disambiguation; the user-scope one is reachable directly by /review.
In the slash-command picker, type /acn- and Claude filters to all toolkit-provided commands.
V1 invocation table
Section titled “V1 invocation table”| Plugin | Skill | Invocation |
|---|---|---|
acn-base-sdlc | review | /acn-base-sdlc:review |
acn-base-sdlc | tdd | /acn-base-sdlc:tdd |
acn-base-sdlc | commit | /acn-base-sdlc:commit |
acn-base-sdlc | pr | /acn-base-sdlc:pr |
acn-slide-gen | generate | /acn-slide-gen:generate |
acn-pursuit-toolkit | rfp-synthesize | /acn-pursuit-toolkit:rfp-synthesize |
acn-pursuit-toolkit | win-theme-builder | /acn-pursuit-toolkit:win-theme-builder |
Skills vs. slash commands
Section titled “Skills vs. slash commands”Not every plugin capability is exposed as a slash command. Skills can also auto-match from context — Claude picks them up when the conversation matches their description frontmatter. Slash commands are the explicit-invocation surface for skills that benefit from a direct handle, typically because they take arguments or run a known workflow.
The full ruleset for what becomes a skill, a rule, or a slash command lives in Adding a Skill.