Plugin Structure

Structure Claude Code plugins with valid plugin.json manifests and auto-discovery.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Tashima-Tarsh/Disha --skill plugin-structure-tashima-tarsh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Plugin Structure
Source: https://github.com/Tashima-Tarsh/Disha/tree/main/disha/services/integrations/Anthropic/plugins/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/Tashima-Tarsh/Disha --skill plugin-structure-tashima-tarsh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates common failures and frustration when building Claude Code plugins, which often break due to incorrect directory layouts, invalid plugin.json manifests, or misorganized components that fail auto-discovery.

Core Features & Use Cases

  • Full Plugin Architecture Reference: Covers standard directory structure, required and optional plugin.json fields, component organization for commands, agents, skills, and hooks, and auto-discovery rules.
  • Portable Path Guidance: Teaches correct use of the ${CLAUDE_PLUGIN_ROOT} environment variable to avoid path resolution errors across operating systems, installation methods, and user environments.
  • Scalable Organization Patterns: Provides advanced patterns for large, team-maintained plugins, including categorized component directories, shared utility libraries, and multi-environment configuration management.
  • Use Case: A developer building a team-wide DevOps automation plugin can use this skill to correctly structure their CI commands, Kubernetes management agents, and security hooks, ensuring all components load automatically for every team member.

Quick Start

Use the Plugin Structure skill to build a new Claude Code plugin with the correct directory layout, valid manifest configuration, and properly organized components for your specific use case.

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 standardized directory layout with categorized folders for commands, agents, skills, and hooks, plus a valid plugin.json manifest, ensuring all components load automatically during auto-discovery.

Why does my Claude Code plugin fail to load components?

Claude Code plugins fail to load components due to incorrect directory layouts, invalid plugin.json manifest fields, or misorganized components that break the auto-discovery mechanism. Fixing the directory structure and manifest resolves these loading failures.

How do I use the CLAUDE_PLUGIN_ROOT environment variable for portable paths?

Use the CLAUDE_PLUGIN_ROOT environment variable to define portable path references in your plugin configuration, avoiding path resolution errors across different operating systems, installation methods, and user environments.

What is the best way to organize a large team-maintained Claude Code plugin?

The best way to organize large team-maintained Claude Code plugins is using scalable organization patterns, including categorized component directories, shared utility libraries, and multi-environment configuration management to support enterprise-grade plugin architectures.

Does Claude Code plugin structure support MCP server integrations?

Yes, Claude Code plugin structure supports MCP server integrations alongside commands, agents, skills, and hooks, allowing developers to build enterprise-grade plugins that automatically discover and load all integrated components.