plugin-structure

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code plugin authors often struggle to organize manifests, component folders, and portable paths so discovery works consistently and the project stays maintainable.

Core Features & Use Cases

  • Plugin layout guidance: Defines where the manifest, commands, agents, skills, hooks, and MCP configuration belong.
  • Discovery and portability rules: Explains how default and custom paths are loaded, and how to keep references portable across installations.
  • Skill organization patterns: Shows how to structure skill subdirectories with supporting references and reusable resources.
  • Use cases: Ideal for scaffolding a new plugin, auditing an existing plugin structure, or standardizing a team’s plugin conventions.

Quick Start

Ask Claude to review or scaffold a Claude Code plugin directory using this skill’s conventions for manifests, component folders, and naming.

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 reliable auto-discovery?

Claude Code plugin auto-discovery requires a root .claude-plugin/plugin.json manifest and standardized component subdirectories. Using kebab-case identifiers for commands, agents, and skills ensures the plugin validates and loads correctly during runtime.

What is the correct file path layout for Claude Code plugin manifests and components?

The correct file path layout for Claude Code plugins places the manifest at .claude-plugin/plugin.json. Components such as commands, agents, skills, hooks, and MCP servers reside in standardized relative subdirectories to ensure portable path handling across installations.

How do I scaffold a new Claude Code plugin with standardized naming conventions?

Scaffold a Claude Code plugin by creating a root plugin.json manifest and defining component folders using kebab-case identifiers. This naming convention standardizes validation across commands, agents, skills, and hooks for maintainable project architecture.

Why does my Claude Code plugin fail validation during component discovery?

Claude Code plugin validation fails during component discovery when the directory lacks a root .claude-plugin/plugin.json manifest or when subdirectories for skills, commands, and agents do not use compliant relative paths and kebab-case identifiers.

Can I use custom paths for Claude Code plugin skills and hooks instead of default directories?

You can use custom paths for Claude Code plugin skills and hooks, but you must configure them correctly within the plugin manifest. Maintaining standardized relative paths ensures portable path handling so references resolve consistently across different installation environments.