Plugin Structure

Create a directory with a `.claude-plugin/plugin.json` manifest containing at least a kebab-case `name` field, then add component folders like `commands/`, `agents/`, or `skills/` at the plugin root. Claude Code auto-discovers all `.md` files in these directories when the plugin is enabled.

The manifest must be at `.claude-plugin/plugin.json` inside the plugin root. Component directories like commands and agents must sit at the plugin root level, not nested inside `.claude-plugin/`.

It is an environment variable resolving to the plugin's install location, used for hook commands, MCP server arguments, and script references. Using it avoids hardcoded absolute paths that break across different installation methods and operating systems.

Common causes are wrong directory placement, missing or malformed YAML frontmatter, or a skill lacking a `SKILL.md` file. Verify the file sits in the correct root-level directory, uses kebab-case naming, and that the plugin is enabled.

Yes, the `commands` and `agents` fields in plugin.json accept a path string or array of paths. These custom paths supplement the default directories rather than replacing them, and each path must be relative and start with `./`.