Plugin Structure

Organize Claude Code plugin components into a predictable directory structure.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/ricable/mcai --skill plugin-structure-ricable
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/ricable/mcai/tree/main/.agents/skills/plugin-structure
Command: npx skills add https://github.com/ricable/mcai --skill plugin-structure-ricable

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork from structuring Claude Code plugins by showing how to arrange commands, agents, skills, hooks, and shared resources so they are easy to discover, maintain, and extend.

Core Features & Use Cases

  • Plugin Layout Guidance: Defines the expected root-level directory structure and where each component type belongs.
  • Manifest and Path Rules: Explains how to configure plugin metadata, custom component paths, and portable references.
  • Skill Organization Patterns: Shows how to group related skills with supporting references, scripts, and assets for scalable workflows.
  • Use Cases: Ideal for plugin authors creating new plugins, refactoring messy component layouts, or documenting team standards for Claude Code automation.

Quick Start

Create a new plugin or skill directory, add a SKILL.md entry point with the correct frontmatter, and organize any supporting files into the appropriate component folders.

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 with commands, agents, and skills?

To structure a Claude Code plugin, organize components into a predictable directory layout with a root manifest, kebab-case naming, relative path configuration, and separated scripts, references, and assets.

What is the recommended directory layout for MCP-enabled workflows?

The recommended directory layout for MCP-enabled workflows requires disciplined separation of scripts, references, and assets, guided by a root manifest and clear component organization for maintainable packaging.

How do I configure a root manifest for custom component paths?

Configuring a root manifest for custom component paths requires using relative path configuration to ensure portable references and predictable discovery across commands, agents, and skills.

Does building a Claude Code plugin require kebab-case naming?

Yes, building a Claude Code plugin requires kebab-case naming for files and directories to ensure predictable discovery and maintainable packaging across commands, hooks, and MCP-enabled workflows.

What's the best way to organize related skills with supporting references and assets?

The best way to organize related skills is grouping them with supporting references, scripts, and assets using disciplined separation and a root manifest, ensuring scalable workflows and clear skill discovery.

When should I refactor a messy plugin component layout?

You should refactor a messy plugin component layout when your commands, agents, skills, and hooks lack clear discovery, requiring a root manifest and relative path configuration for maintainable packaging.