how-plugins-work

Document Claude Code plugin, skill, and marketplace naming resolution rules.

3|1|Updated Apr 4, 2026

Search Tags:#autocomplete #plugin #skill #claude-code #naming #invocation #slash-command

Ready to run

npx skills add https://github.com/epologee/leclause-skills --skill how-plugins-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: how-plugins-work
Source: https://github.com/epologee/leclause-skills/tree/main/packages/how-plugins-work/skills/how-plugins-work
Command: npx skills add https://github.com/epologee/leclause-skills --skill how-plugins-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Disambiguates how Claude Code resolves plugin, skill, and marketplace names to prevent Unknown command errors and broken autocomplete by clarifying the three-name model and invocation patterns.

Core Features & Use Cases

Explains the separate namespaces: Plugin name, Skill name, and Marketplace name, and how Claude Code combines them in various contexts.
Provides practical scenarios showing when to use bare slash commands vs namespaced invocations to avoid collisions.
Serves as a reference for debugging name-resolution issues across plugins and bundles.

Quick Start

Explain how plugin:skill resolution works for how-plugins-work to resolve Unknown command.

Frequently Asked Questions about how-plugins-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How does Claude Code plugin naming and slash-command resolution work?▼

Claude Code plugin naming uses a three-name model: Plugin name, Skill name, and Marketplace name. The system combines these namespaces differently depending on the context to resolve slash commands and populate autocomplete suggestions.

Why do I get Unknown command errors when invoking a plugin skill?▼

Unknown command errors occur when Claude Code cannot resolve a slash command due to name collisions or incorrect invocation syntax. Using the proper namespaced invocation pattern instead of a bare slash command disambiguates the target skill and fixes the resolution failure.

When should I use bare slash commands versus namespaced invocations in Claude Code?▼

Use bare slash commands for simple, single-context scenarios, and switch to namespaced invocations when debugging name collisions across multiple plugins or bundles. Namespacing prevents conflicts by explicitly routing the command to the correct plugin and skill.

How do I fix broken autocomplete for installed Claude Code skills?▼

Broken autocomplete stems from improper skill naming conventions and unresolved namespace collisions. Clarifying the three-name model and ensuring the plugin, skill, and marketplace names follow resolution rules restores correct autocomplete behavior.

What are the naming rules for avoiding plugin name collisions in Claude Code?▼

Plugin name collisions are avoided by understanding the separate namespaces for Plugin, Skill, and Marketplace names. Documenting how these names combine and applying the correct resolution patterns prevents invocation conflicts across installed bundles.