From claude-code-docs
Claude Code plugins configuration reference. Use when creating plugins, bundling commands/agents/hooks/skills/MCP servers, setting up marketplaces, or distributing extensions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-docs:plugins-referenceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Plugins bundle commands, agents, skills, hooks, and MCP servers into distributable packages.
Plugins bundle commands, agents, skills, hooks, and MCP servers into distributable packages.
my-plugin/
├── .claude-plugin/
│ └── plugin.json # Required: plugin manifest
├── commands/ # Slash commands
│ └── deploy.md
├── agents/ # Subagent definitions
│ └── reviewer.md
├── skills/ # Agent skills
│ └── api-patterns/
│ └── SKILL.md
├── hooks/
│ └── hooks.json # Hook configurations
├── .mcp.json # MCP server configs
└── .lsp.json # LSP server configs
{
"name": "my-plugin",
"version": "1.0.0",
"description": "Plugin description",
"author": {
"name": "Author Name",
"email": "author@example.com"
},
"keywords": ["keyword1", "keyword2"]
}
| Field | Required | Description |
|---|---|---|
name | Yes | Unique identifier (kebab-case) |
version | No | Semantic version |
description | No | Brief description |
author | No | Author info |
commands | No | Custom command paths |
agents | No | Custom agent paths |
skills | No | Custom skill paths |
hooks | No | Hook config path/object |
mcpServers | No | MCP config path/object |
lspServers | No | LSP config path/object |
| Scope | Location | Use Case |
|---|---|---|
user | ~/.claude/settings.json | Personal (default) |
project | .claude/settings.json | Team shared |
local | .claude/settings.local.json | Project, gitignored |
Install plugin:
/plugin install plugin-name@marketplace
claude plugin install plugin-name@marketplace --scope project
Uninstall plugin:
/plugin uninstall plugin-name
Enable/Disable:
/plugin enable plugin-name
/plugin disable plugin-name
Update plugin:
/plugin update plugin-name
Validate plugin:
/plugin validate ./path/to/plugin
claude plugin validate ./path/to/plugin
{
"name": "my-marketplace",
"owner": {
"name": "Team Name"
},
"plugins": [
{
"name": "plugin-name",
"source": "./plugins/plugin-name",
"description": "Plugin description"
}
]
}
# Add marketplace
/plugin marketplace add owner/repo
/plugin marketplace add https://gitlab.com/org/plugins.git
# Update marketplaces
/plugin marketplace update
# List marketplaces
/plugin marketplace list
{ "source": "./plugins/my-plugin" }
{
"source": {
"source": "github",
"repo": "owner/repo"
}
}
{
"source": {
"source": "url",
"url": "https://gitlab.com/org/plugin.git"
}
}
Use ${CLAUDE_PLUGIN_ROOT} in hooks and MCP configs:
{
"hooks": {
"PostToolUse": [{
"hooks": [{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/format.sh"
}]
}]
}
}
Add to .claude/settings.json:
{
"extraKnownMarketplaces": {
"company-tools": {
"source": {
"source": "github",
"repo": "org/claude-plugins"
}
}
},
"enabledPlugins": {
"formatter@company-tools": true
}
}
| Issue | Solution |
|---|---|
| Plugin not loading | Check plugin.json syntax |
| Commands missing | Ensure commands/ at root, not in .claude-plugin/ |
| Hooks not firing | Check script permissions (chmod +x) |
| MCP fails | Use ${CLAUDE_PLUGIN_ROOT} for paths |
# Debug mode shows plugin loading
claude --debug
# Check for errors
/plugin # Navigate to Errors tab
For complete documentation, see:
npx claudepluginhub DuncanJurman/entropy-plugins --plugin claude-code-docsFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.