Plugin Structure

Scaffolds Claude Code plugin directories with manifests and SKILL.md files.

1|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/Invictusprime7/unison-tasks-official --skill plugin-structure-invictusprime7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/Invictusprime7/unison-tasks-official/tree/main/claude-code-main/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/Invictusprime7/unison-tasks-official --skill plugin-structure-invictusprime7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge base helps developers who want to build, organize, and maintain Claude Code plugins by providing a standardized structure, clear guidance on manifests, and consistent component layouts.

Core Features & Use Cases

  • Establishes a canonical plugin directory layout (root/.claude-plugin, commands, agents, skills, hooks, mcp.json) and a predictable skill discovery flow.
  • Guides the creation of SKILL.md frontmatter for each skill to enable autonomous loading and activation.
  • Defines naming conventions, auto-discovery rules, and portable path references to ensure cross-platform compatibility and maintainability.

Quick Start

Create a new plugin directory with a root .claude-plugin/plugin.json and a skills/ subdirectory containing your first SKILL.md.

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 directory for auto-discovery?

To structure a Claude Code plugin, create a root .claude-plugin/plugin.json file alongside subdirectories for commands, agents, skills, and hooks. This establishes a predictable skeleton that enables the system's auto-discovery patterns to find and load your components automatically.

What is a SKILL.md frontmatter schema and why do I need it?

A SKILL.md frontmatter schema is a required metadata block at the top of each skill file that enables autonomous loading and activation. It defines naming conventions and activation criteria so the Claude Code environment can discover and trigger your skills without manual configuration.

What's the best way to scaffold a new Claude Code plugin?

The best way to scaffold a Claude Code plugin is to start with a root .claude-plugin/plugin.json manifest and a skills/ subdirectory containing your first SKILL.md. Following this standardized layout ensures cross-platform compatibility and maintainability across all plugin components.

Does a Claude Code plugin require a manifest file to work?

Yes, a Claude Code plugin requires a root .claude-plugin/plugin.json manifest to function properly. This manifest defines the plugin's structure, enables auto-discovery for commands and agents, and enforces the standardized skeleton needed for portable path references.

How does auto-discovery work for Claude Code plugin components like hooks and agents?

Auto-discovery for Claude Code plugin components works by scanning the canonical directory layout for commands, agents, skills, and hooks. When each component follows the defined naming conventions and SKILL.md frontmatter schema, the system automatically loads and activates them without explicit registration.

Why do my Claude Code plugin skills fail to activate during runtime?

Plugin skills fail to activate when the SKILL.md frontmatter schema is missing or incorrectly formatted. Ensuring each skill file contains the required frontmatter and follows the established naming conventions will satisfy the discovery and activation rules needed for autonomous loading.