plugin-structure

Guide Claude Code plugin development with standardized directory and manifest configuration.

Updated May 3, 2026
One-click install
npx skills add https://github.com/skogai/marketplace --skill plugin-structure-skogai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-structure
Source: https://github.com/skogai/marketplace/tree/main/plugin-dev/skills/plugin-structure
Command: npx skills add https://github.com/skogai/marketplace --skill plugin-structure-skogai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill resolves ambiguity in Claude Code plugin development by providing a standardized framework for directory organization, manifest configuration, and component discovery.

Core Features & Use Cases

  • Standardized Architecture: Provides clear rules for structuring commands, agents, skills, and hooks to ensure seamless auto-discovery.
  • Manifest Configuration: Offers deep guidance on setting up plugin.json, including custom path resolution and metadata best practices.
  • Use Case: When building a new plugin, use this Skill to ensure your component paths are portable using the CLAUDE_PLUGIN_ROOT variable and that your manifest follows semantic versioning and naming conventions.

Quick Start

Ask the plugin-structure skill to scaffold a new plugin directory with the standard manifest and 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 for auto-discovery?

To structure a Claude Code plugin for auto-discovery, organize commands, agents, skills, and hooks within a standardized directory framework. This ensures the system seamlessly detects and loads your plugin components without manual path configuration.

What is the CLAUDE_PLUGIN_ROOT variable used for in plugin development?

The CLAUDE_PLUGIN_ROOT variable is used for portable path resolution in plugin development. By referencing this variable in your manifest and scripts, you ensure component paths remain stable across different installation environments.

How do I configure the plugin.json manifest for a Claude Code plugin?

Configuring the plugin.json manifest requires defining metadata, custom paths, and semantic versioning. Following naming conventions in the manifest ensures your plugin is correctly parsed, versioned, and integrated by the Claude Code architecture.

Does Claude Code plugin development require a specific directory structure?

Claude Code plugin development requires a specific directory structure to enable component auto-discovery. Standardized architectural rules dictate how commands, agents, skills, and hooks are organized to ensure seamless system integration.

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

The best way to scaffold a new Claude Code plugin is to generate a standardized directory structure with the standard manifest and component folders. This approach ensures your plugin architecture follows portable path resolution and auto-discovery mechanisms from the start.