plugin-development

Create, structure, and debug Claude Code plugins with manifests and directory layouts.

10|1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/GGPrompts/my-gg-plugins --skill plugin-development-ggprompts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-development
Source: https://github.com/GGPrompts/my-gg-plugins/tree/main/skills/plugin-development
Command: npx skills add https://github.com/GGPrompts/my-gg-plugins --skill plugin-development-ggprompts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides you through creating, structuring, and debugging Claude Code plugins, reducing the complexity of plugin development and marketplace preparation.

Core Features & Use Cases

  • Structured Plugin Layout: Learn where to place manifests, commands, agents, skills, and MCP server definitions.
  • Debugging & Marketplace Readiness: Understand common pitfalls and how to debug loading and configuration.
  • Publish-Ready Workflows: Prepare plugins for distribution via marketplaces with correct paths and manifests.

Quick Start

Create a new plugin folder name "my-plugin" with:

  • .claude-plugin/plugin.json at the root (requires manifest)
  • at least one commands/, agents/, or skills/ directory
  • a sample skills/my-skill/SKILL.md with proper frontmatter

Frequently Asked Questions about plugin-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Claude Code plugin from scratch?

Create a plugin folder with a `.claude-plugin/plugin.json` manifest at the root, add at least one `commands/`, `agents/`, or `skills/` directory, and include a sample `skills/my-skill/SKILL.md` with proper frontmatter. This structured layout ensures Claude Code recognizes and loads your plugin correctly.

What should I include in my plugin.json manifest?

The plugin.json manifest is required in `.claude-plugin/` at your plugin root and defines plugin metadata, component references, and marketplace information. It tells Claude Code how to load commands, agents, skills, and MCP servers from your plugin directory structure.

Why isn't my Claude Code plugin loading?

Plugin loading failures typically stem from missing or malformed plugin.json, incorrect directory paths, or components not placed in expected `commands/`, `agents/`, or `skills/` folders. Verify manifest syntax, check relative paths enforce proper nesting, and confirm all component definitions reference existing files.

How do I prepare my plugin for marketplace publishing?

Ensure your plugin follows the structured layout, includes a valid plugin.json with marketplace metadata, tests all components for correct loading, and documents features in component SKILL.md files with proper frontmatter. This publish-ready workflow reduces configuration errors and speeds marketplace distribution.

Can I extend Claude Code with custom MCP servers in my plugin?

Yes, Claude Code plugins support MCP server definitions alongside commands, agents, and skills. Place server definitions in your plugin structure and reference them in plugin.json to extend Claude Code functionality with custom protocol integrations.

What are common pitfalls when debugging plugin configuration?

Common issues include relative path mismatches, missing manifest files, malformed SKILL.md frontmatter, and component definitions not aligned with directory layout. Debug by validating plugin.json syntax, confirming file paths match manifest references, and testing each component loads independently.