Agent skill · software engineering · aiskillstore
plugin-structure
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.
Why this skill is useful
Provides detailed directory structure and configuration patterns for Claude Code plugins that the AI wouldn't reliably generate on its own.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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: Critical rules: 1. Manifest location: The plugin.json manifest MUST be in .claude-plugin/ directory 2. Component locations: All component directories (commands, agents, skills, hooks) MUST be at plugin root level, NOT nested inside .claude-plugin/ 3. Optional components: Only create directories for components the plugin actually uses 4. Naming convention: Use kebab-case for all directory and file names Plugin Manifest (plugin.json) The manifest defines plugin metadata and configuration. Located at .claude-plugin/plugin.json: Required Fields Name requirements: Use kebab-case format (lowercase with hyphens) Must be unique across installed plugins No spaces or special characters Example: code-review-assistant, test-runner, api-docs Recommended Metadata Version format: Follow semantic versioning (MAJOR.MINOR.PATCH) Keywords: Use for plugin discovery and categorization Component Path Configuration Specify custom paths for components (supplements default directories): Important: Custom paths supplement defaults—they don't replace them. Components in both default directories and custom paths will load. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/plugin-structure--b8f704