Repository navigation
Claude Code Plugins
xsyetopz edited this page Oct 19, 2026
·
1 revision
A plugin is a folder that adds skills, agents, hooks, or MCP servers to Claude Code.
A marketplace is a list of plugins that you can install.
For example, claude plugin install my-plugin@my-marketplace installs a plugin from a marketplace.
| Mark | Meaning |
|---|---|
| ✅ | A page of the Claude Code docs names it. |
| 🔍 | Only the Claude Code bundle names it. No docs page does. |
| The docs and the bundle differ. The row says how. | |
| 🧪 | It works only behind a flag, a plan, or a server-side switch. The row says which. |
| ❌ | It is removed or does nothing in 2.1.303. |
| Page | Content |
|---|---|
| Manifest | Each plugin.json key, userConfig, component layout |
| Marketplace | Each marketplace.json key, plugin and marketplace sources, settings keys |
| Loader | Paths, cache, variables, env vars, enabling |
| CLI | Each claude plugin subcommand, /plugin, flags |
- A plugin is a folder with an optional
.claude-plugin/plugin.json. Its parts are skills, commands, agents, hooks, MCP servers, LSP servers, monitors, output styles, workflows, themes,bin/, and mods. - A marketplace lists plugins in
.claude-plugin/marketplace.json. - A plugin id is
name@marketplace. Special marketplaces:inline(session flags),builtin,skills-dir,synced. - Enable state is in
enabledPlugins. Scopes areuser,project,local, andmanaged. - Plugin skills are namespaced as
/<plugin>:<skill>. See Skills and Commands.
- Create Plugins is the docs page for authors.
-
Plugin Manifest Reference is the docs page for
plugin.json. - Skills And Commands covers the skills that plugins ship.
- Mod API covers mods.
claudetto
- Start
- Slices
- Add-Ons
- Reference
- Rationale
- Evidence
- Development
Claude Code 2.1.303
- Start
- Models and Context
- Configure
- Extend
- Findings