skills.rest
Tx1207
Tx1207COMMUNITY
Explore all skills by this author →
GitHub

plugin-structure

Describe Claude Code plugin structure patterns and validate SKILL.md frontmatter.

5|2|Updated Jul 2, 2026
Search Tags:#best-practices#claude-code#auto-discovery#plugin-structure#markdown-frontmatter#component-organization#plugin-manifest
One-click install
npx skills add https://github.com/Tx1207/hello-scholar --skill plugin-structure-tx1207
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/Tx1207/hello-scholar/tree/main/skills/meta/plugin-structure
Command: npx skills add https://github.com/Tx1207/hello-scholar --skill plugin-structure-tx1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill provides clear guidance on Claude Code plugin structure and best practices to help teams scaffold, organize, and discover plugin components efficiently.

Core Features & Use Cases

  • Clear manifest guidance for .claude-plugin/plugin.json structure and minimal fields
  • Guidance on component organization (commands, agents, skills, hooks) and auto-discovery rules
  • Portability and naming conventions to support cross-platform usage and maintainability

Quick Start

Create a new plugin skeleton following these guidelines and add a SKILL.md with proper frontmatter.

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?▼

Claude Code plugin structure requires a .claude-plugin/plugin.json manifest and a SKILL.md file with proper markdown frontmatter to enable component auto-discovery. Commands, agents, skills, and hooks are then organized into dedicated directories.

What fields are required in a Claude Code plugin manifest?▼

A Claude Code plugin manifest located at .claude-plugin/plugin.json requires minimal foundational fields to define the plugin identity and enable auto-discovery. These manifest requirements ensure the plugin structure validates correctly.

What are the best practices for naming Claude Code plugin components?▼

Claude Code plugin best practices dictate using naming conventions that support portability and cross-platform maintainability. Component organization rules ensure that commands, agents, skills, and hooks are consistently discovered.

Why is my Claude Code plugin not auto-discovering components?▼

Auto-discovery fails when the plugin structure lacks a valid SKILL.md with proper markdown frontmatter, or when the .claude-plugin/plugin.json manifest is missing required fields. Validate that optional resource directories exist as needed.

Do I need a SKILL.md file for every Claude Code plugin?▼

Yes, a SKILL.md file with proper markdown frontmatter is mandatory for Claude Code plugin structure validation. It ensures the plugin meets auto-discovery rules and allows component organization to be parsed correctly.

What's the best way to organize a Claude Code plugin directory layout?▼

The best way to organize a Claude Code plugin directory is to follow component organization guidelines, separating commands, agents, skills, and hooks. This directory layout ensures portability and aligns with auto-discovery rules.

Related Skills

Explore More Software Engineering Skills→
LusciiLuscii

terraform-modules

Design reusable Terraform modules with standard structures and provider configurations.

Official
Advanced
susomejiassusomejias
9

Plugin Structure

Structure Claude Code plugins with plugin.json manifests and portable path references.

Community
Intermediate
ddaanetddaanet

plugin-dev-validation

Define and enforce domain validation criteria for plugin components during artifact review.

Community
Advanced
victorjoshi9victorjoshi9
1

plugin-structure

Organize Claude Code plugin directories with manifests and kebab-case identifiers.

Community
Advanced