plugin-structure

Scan skill roots for SKILL.md and validate frontmatter metadata.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/GongXLiang/plot-study --skill plugin-structure-gongxliang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/GongXLiang/plot-study/tree/main/.claude/plugins/marketplaces/claude-plugins-official/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/GongXLiang/plot-study --skill plugin-structure-gongxliang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizes Claude Code plugin development by providing a clear blueprint for directory layout, manifest configuration, component organization, and discovery rules.

Core Features & Use Cases

  • Directory structure guidance for commands, agents, skills, and hooks.
  • Manifest configuration basics with plugin.json and optional component paths.
  • Auto-discovery rules for default and custom component locations, plus portable path references.
  • Practical examples and patterns to bootstrap minimal and full-featured plugins.

Quick Start

Create a plugin directory with a .claude-plugin/plugin.json manifest and a skills/ subfolder containing SKILL.md entries.

Frequently Asked Questions about plugin-structure

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

FAQPage Schema
What is the required directory structure for a Claude Code plugin?

A valid Claude Code plugin structure requires a root directory with a .claude-plugin/plugin.json manifest and a skills/ subfolder containing SKILL.md entries to define valid Skill Units.

How do I configure plugin.json manifest and auto-discovery rules?

Configure plugin.json by defining plugin metadata and optional component paths. Auto-discovery rules scan default locations and custom paths to identify valid Skill Units and optional resources.

Does a valid Skill Unit require a specific manifest format?

Yes, a valid Skill Unit requires a root SKILL.md file where the frontmatter explicitly defines the name and description fields to pass metadata validation checks.

What optional resources can be detected under plugin directory structures?

The plugin directory structure supports detecting optional resources organized under scripts/, references/, and assets/ subfolders to provide extended functionality for Skill Units.

What metadata is evaluated when scanning SKILL.md files?

Scanning SKILL.md files evaluates metadata including name, tagline, description, request, complexity, category, keywords, dependencies, components, and toxicity assessment for each valid Skill Unit.

When should I use custom component locations instead of default discovery paths?

Use custom component locations when your plugin requires non-standard directory layouts, enabling portable path references and overriding default auto-discovery rules for commands, agents, and hooks.