claude-code-plugin-development

Package Claude Code plugin components into distributable plugins with a plugin.json manifest.

23|2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/dwmkerr/claude-toolkit --skill claude-code-plugin-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-plugin-development
Source: https://github.com/dwmkerr/claude-toolkit/tree/main/plugins/toolkit/skills/claude-code-plugin-development
Command: npx skills add https://github.com/dwmkerr/claude-toolkit --skill claude-code-plugin-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers package Claude Code plugins by bundling commands, agents, skills, hooks, MCP servers, and LSP servers into a distributable plugin package.

Core Features & Use Cases

  • Packaging: Assemble plugin components at root (plugin.json, commands/, agents/, skills/, hooks/, etc.) for distribution.
  • Marketplace readiness: Ensure manifests and component structure align with Claude Code plugin requirements.
  • Quick validation: Validate structure against Marketplace/Plugin Manifest guidelines to enable seamless installation and deployment.

Quick Start

To start, create a distributable plugin by organizing your plugin into a root plugin folder with a manifest at .claude-plugin/plugin.json, place commands, agents, and skills at root-level directories, and run your packaging workflow.

Frequently Asked Questions about claude-code-plugin-development

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

FAQPage Schema
How do I package Claude Code plugins for distribution?

To package a Claude Code plugin, organize components into root-level directories like commands/, agents/, skills/, and hooks/, then create a manifest at .claude-plugin/plugin.json to bundle everything into a distributable package.

What is a Claude Code plugin manifest and how does it work?

A Claude Code plugin manifest is a plugin.json file placed at the .claude-plugin/ root directory. It defines the plugin's structure and components, enabling the system to validate and install bundled commands, agents, and hooks seamlessly.

Can I bundle MCP servers and LSP servers into a Claude Code plugin?

Yes, you can bundle MCP servers and LSP servers into a Claude Code plugin. The packaging process supports assembling these server components alongside commands, agents, skills, and hooks within the distributable plugin structure.

What's the best way to validate a Claude Code plugin before publishing to a marketplace?

The best way to validate a Claude Code plugin for marketplace readiness is to check its structure against marketplace guidelines, ensuring the root-level .claude-plugin/plugin.json manifest and component placement are correctly configured for deployment.

Does a Claude Code plugin require a specific directory structure for hooks and scripts?

Yes, Claude Code plugins require proper component placement, such as a hooks/ directory for hooks. Optional support directories like scripts/, references/, and assets/ can also be included at the root level as needed for the plugin's functionality.