plugin structure — Skills — getagentictools

What it does

Conventional directory layout for automatic discovery

Manifest-driven configuration in .claude-plugin/plugin.json

Component-based organization (commands, agents, skills, hooks)

Portable path references using ${CLAUDEPLUGINROOT}

Explicit vs. auto-discovered component loading

Use kebab-case format (lowercase with hyphens)

Must be unique across installed plugins

plugin structure

Source

Repository: https://github.com/anthropics/claude-code

plugin structure FAQ

What does the plugin structure skill do?

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices. Conventional directory layout for automatic discovery Manifest-driven configuration in .claude-plugin/plugin.json

What does plugin structure require?

Configuration keys: SKILL, README, CLAUDE_PLUGIN_ROOT.

How do I install plugin structure?

Run: npx -y skills add https://github.com/anthropics/claude-code --skill plugin structure --agent claude-code — the source lives at github.com/anthropics/claude-code.

Maintain plugin structure?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![plugin structure on getagentictools](https://getagentictools.com/badge/skills/anthropics-claude-code-plugin-structure.svg)](https://getagentictools.com/skills/anthropics-claude-code-plugin-structure?ref=badge)

npx agentictools info skills/anthropics-claude-code-plugin-structure

The second line is the CLI lookup for this page — handy in READMEs and docs.