plugin-structure

Validate Claude Code plugin structures for required SKILL.md frontmatter and manifest paths.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill plugin-structure-avatar-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/AvaTar-ArTs/my-supremepowers/tree/main/qwen_skills/plugin-structure
Command: npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill plugin-structure-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies and standardizes how Claude Code plugins are organized, making it easy to scaffold correct plugin structures and minimize configuration errors.

Core Features & Use Cases

  • Defines a consistent plugin root layout (plugin root, .claude-plugin/plugin.json, commands/, agents/, skills/, hooks/, .mcp.json) and optional subdirectories (scripts/, references/, assets/).
  • Enforces manifest-based configuration and portable path references using ${CLAUDE_PLUGIN_ROOT} to support multi-environment deployments.
  • Guides auto-discovery, naming conventions, and maintenance practices to streamline plugin development and onboarding.

Quick Start

Create a new plugin skeleton at the plugin root, add a SKILL.md in each skill directory, and use ${CLAUDE_PLUGIN_ROOT} for all internal paths.

Frequently Asked Questions about plugin-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Claude Code plugin for auto-discovery?

To structure a Claude Code plugin for auto-discovery, organize the root with .claude-plugin/plugin.json and use directories like commands/, agents/, skills/, and hooks/. Every skill directory must contain a SKILL.md with required frontmatter for valid component detection.

What is ${CLAUDE_PLUGIN_ROOT} used for in plugin development?

${CLAUDE_PLUGIN_ROOT} is used for creating portable path references within your plugin manifest and scripts. It resolves internal paths dynamically, ensuring your plugin deployments work reliably across multiple environments without hardcoding absolute directory locations.

What directories are required when scaffolding a Claude Code plugin layout?

Required directories for a Claude Code plugin layout include commands/, agents/, skills/, and hooks/, alongside the .claude-plugin/plugin.json manifest. Optional directories like scripts/, references/, and assets/ can be added to support extended plugin functionality.

Does every Claude Code skill need a SKILL.md file to be valid?

Yes, every Claude Code skill needs a SKILL.md file to be valid. The plugin structure validation process enforces this requirement, ensuring each skill directory contains the necessary frontmatter for proper auto-discovery, versioning, and maintainable plugin deployments.

How do I minimize configuration errors when setting up a plugin manifest?

To minimize configuration errors in a plugin manifest, enforce strict naming conventions and use manifest-based configuration. Defining a consistent plugin root layout with .claude-plugin/plugin.json and validating component structures ensures reliable auto-discovery and reduces setup failures.

Can I use custom scripts and assets in my Claude Code plugin structure?

Yes, you can use custom scripts and assets in your Claude Code plugin structure by adding optional scripts/, references/, and assets/ directories. These are resolved dynamically via the manifest using ${CLAUDE_PLUGIN_ROOT} paths to support extended functionality.