plugin-structure Skill
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 ${CLAUDEPLUGINROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest con Published by anthropics in claude-plugins-official.
What is plugin-structure Skill?
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 ${CLAUDEPLUGINROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest con Published by anthropics in claude-plugins-official. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using claude-plugins-official
Technical details
- Install or run with Copy skill directory
When to use plugin-structure Skill
- Use it for developers using claude-plugins-official.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/claude-plugins-official
- Skill file: plugins/plugin-dev/skills/plugin-structure/SKILL.md
What it does
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 ${CLAUDEPLUGINROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest con
Skill instructions
Plugin Structure for Claude Code Overview Claude Code plugins follow a standardized directory structure with automatic component discovery. Understanding this structure enables creating well-organized, maintainable plugins that integrate seamlessly with Claude Code. Key concepts: - 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 Directory Structure Every Claude Code plugin follows this organizational pattern: plugin-name/ ├── .claude-plugin/ │ └── plugin.json Required: Plugin manifest ├── commands/ Slash commands (.md files) ├── agents/ Subagent definitions (.md files) ├── skills/ Agent skills (subdirectories) │ └── skill-name/ │ └── SKILL.md Required for each skill ├── hooks/ │ └── hooks.json Event handler configuration ├── .mcp.json MCP server definitio
Explore related resources
Frequently asked questions
What is plugin-structure?
plugin-structure is a open-source AI agent skill with Copy skill directory. 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 ${CLAUDEPLUGINROOT}", "add.
Who is plugin-structure best for?
plugin-structure is best for reusing agent instructions, scripts, and references.
How do I install plugin-structure?
Install or run plugin-structure using Copy skill directory. Check plugin-structure for the latest setup command.
Is plugin-structure actively maintained?
plugin-structure may need a closer maintenance check before production use.
Auto-fetched from GitHub.
