plugin-structure
Guidance for scaffolding Claude Code plugins: directory layout, plugin.json manifest, and component auto-discovery.
🛡️ AgentReady threat assessment
MAESTRO 7-layer threat model + OWASP AIVSS risk score for plugin-structure, derived from its capabilities.
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.
Overview
Part of the plugin-dev plugin, this skill explains Claude Code plugin architecture: directory layout, the plugin.json manifest, the ${CLAUDE_PLUGIN_ROOT} variable, how to add commands/agents/skills/hooks, and how auto-discovery and file-naming conventions work. It provides the structural best practices needed to create or organize a plugin.
Key features and capabilities
- plugin.json manifest configuration
- Component auto-discovery layout
- File-naming and organization conventions
Use cases
- Scaffold a new Claude Code plugin
- Reorganize a plugin's components correctly