Create plugins changedplugins
Nearest release: v2.1.243, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+12added
Lines−12removed
From line
166
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 166, old and new numbered
/
from line 166
166166 The plugin root is the individual plugin's own directory: the one you pass to `--plugin-dir` or that contains `.claude-plugin/plugin.json`. It is never `~/.claude/`. For example, Claude Code doesn't read a `.mcp.json` placed at `~/.claude/.mcp.json`.
167167</Warning>
168168
169| Directory | Location | Purpose |
170| :---------------- | :---------- | :----------------------------------------------------------------------------- |
171| `.claude-plugin/` | Plugin root | Contains `plugin.json` manifest (optional if components use default locations) |
172| `skills/` | Plugin root | Skills as `<name>/SKILL.md` directories |
173| `commands/` | Plugin root | Skills as flat Markdown files. Use `skills/` for new plugins |
174| `agents/` | Plugin root | Custom agent definitions |
175| `hooks/` | Plugin root | Event handlers in `hooks.json` |
176| `.mcp.json` | Plugin root | MCP server configurations |
177| `.lsp.json` | Plugin root | LSP server configurations for code intelligence |
178| `monitors/` | Plugin root | Background monitor configurations in `monitors.json` |
179| `bin/` | Plugin root | Executables added to the Bash tool's `PATH` while the plugin is enabled |
180| `settings.json` | Plugin root | Default [settings](/docs/en/settings) applied when the plugin is enabled |
169| Directory | Location | Purpose |
170| :---------------- | :---------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
171| `.claude-plugin/` | Plugin root | Contains `plugin.json` manifest (optional if components use default locations) |
172| `skills/` | Plugin root | Skills as `<name>/SKILL.md` directories |
173| `commands/` | Plugin root | Skills as flat Markdown files. Use `skills/` for new plugins |
174| `agents/` | Plugin root | Custom agent definitions |
175| `hooks/` | Plugin root | Event handlers in `hooks.json` |
176| `.mcp.json` | Plugin root | MCP server configurations |
177| `.lsp.json` | Plugin root | LSP server configurations for code intelligence |
178| `monitors/` | Plugin root | Background monitor configurations in `monitors.json` |
179| `bin/` | Plugin root | Executables added to the Bash tool's `PATH` while the plugin is enabled. You can't include this directory in a plugin you [distribute through claude.ai organization settings](/docs/en/plugin-marketplaces#keep-executables-out-of-the-top-level-bin-directory) |
180| `settings.json` | Plugin root | Default [settings](/docs/en/settings) applied when the plugin is enabled |
181181
182182A plugin that ships exactly one skill can place `SKILL.md` directly at the plugin root instead of creating a `skills/` directory. Claude Code loads it as a single skill and uses the frontmatter `name` field for the invocation name. Use the `skills/` layout for plugins that may grow to more than one skill.
183183
No line in this hunk matches that.