plugin-development

Scaffold Claude Code plugin structures with skills, agents, hooks, and MCP servers.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/christophevg/c3 --skill plugin-development-christophevg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-development
Source: https://github.com/christophevg/c3/tree/main/skills/plugin-development
Command: npx skills add https://github.com/christophevg/c3 --skill plugin-development-christophevg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creating and maintaining Claude Code plugins is error-prone because users must follow a specific directory layout, manifest rules, and progressive-disclosure conventions to ensure skills and components are discovered and work reliably.

Core Features & Use Cases

  • Plugin architecture guidance: Helps you organize skills, agents, hooks, and optional MCP server configuration into the expected plugin layout.
  • Correct manifest setup: Explains how to place and format .claude-plugin/plugin.json (including recommended metadata and semantic versioning).
  • Skill authoring standards: Provides best practices for SKILL.md frontmatter and instructions so the skill triggers correctly and loads efficiently.
  • Resource organization patterns: Shows how to move detailed content into references/ while keeping SKILL.md lean for faster activation.
  • Validation and distribution workflow: Covers local validation, testing with --plugin-dir, and publishing/distribution considerations for marketplaces and GitHub.

Quick Start

Use this skill when you need to scaffold a new plugin and want Claude Code to auto-discover your skills by following the correct directory layout and .claude-plugin/plugin.json manifest format.

Frequently Asked Questions about plugin-development

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

FAQPage Schema
How do I structure a Claude Code plugin for marketplace distribution?

Claude Code plugin structure requires organizing skills, agents, hooks, and optional MCP server configuration into specific component directories alongside a `.claude-plugin/plugin.json` manifest for marketplace-ready distribution.

What is progressive disclosure in SKILL.md frontmatter and why does it matter?

Progressive disclosure in SKILL.md frontmatter keeps the skill file lean for faster activation while moving detailed content into `references/` directories, ensuring Claude Code discovers and loads skills efficiently without overwhelming the context window.

How do I validate a Claude Code plugin before publishing to a marketplace?

Validate a Claude Code plugin by running `claude plugin validate` to check manifest placement and naming conventions, then test locally using the `--plugin-dir` flag to ensure skills and hooks trigger correctly before marketplace distribution.

Does Claude Code plugin naming require kebab-case and specific manifest placement?

Claude Code plugin naming requires kebab-case formatting, and the manifest must be placed at `.claude-plugin/plugin.json` to satisfy discovery requirements and pass validation checks.

Can I integrate an MCP server configuration into my Claude Code plugin structure?

Yes, you can integrate optional MCP server configuration into your Claude Code plugin structure by organizing it alongside skills, agents, and hooks in the expected directory layout so it remains discoverable and maintainable.

What are the limitations when organizing hooks and skills in a Claude Code plugin?

Limitations when organizing hooks and skills in a Claude Code plugin include strict adherence to the expected directory layout and progressive-disclosure conventions, as deviations prevent Claude Code from auto-discovering components and cause validation failures.