plugin-development

Develop Claude Code plugins with standardized layouts and plugin.json configuration.

18|1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/andisab/swe-marketplace --skill plugin-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-development
Source: https://github.com/andisab/swe-marketplace/tree/main/plugins/context-engineering/skills/plugin-development
Command: npx skills add https://github.com/andisab/swe-marketplace --skill plugin-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps create production-ready Claude Code plugins following Anthropic's official plugin specifications, including plugin.json metadata, typical directory layouts, and distribution workflows.

Core Features & Use Cases

  • Defines plugin metadata, versioning, and marketplace distribution
  • Guides plugin structure (agents/, skills/, commands/, hooks/, mcp/, templates)
  • Illustrates installation/workflow for team usage and deployment
  • Provides examples for plugin README and documentation

Quick Start

Create a plugin named database-toolkit with .claude-plugin/plugin.json and components under a plugin-name/ directory (agents/, skills/, commands/), plus README and CHANGELOG as appropriate.

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 distribution?

A Claude Code plugin requires a .claude-plugin/ directory containing plugin.json metadata, plus component subdirectories (agents/, skills/, commands/, hooks/, mcp/) organized under your plugin-name/ folder. Include a README and CHANGELOG to document features and versioning for marketplace readiness.

What goes in a plugin.json configuration file?

plugin.json defines plugin metadata including name, version, engine compatibility, dependencies, and descriptions. It serves as the manifest that Claude Code reads during installation to validate the plugin against semantic versioning requirements and marketplace standards.

Can I bundle multiple tools and components into a single Claude Code plugin?

Yes. Organize multi-component toolkits by placing agents, skills, commands, and optional MCP integrations in separate subdirectories within your plugin structure. This layout standardizes installation and allows users to deploy coordinated capabilities as one distributable package.

What's the workflow for publishing a plugin to the Claude Code marketplace?

Design your plugin following standardized directory layouts, configure plugin.json with correct versioning and engine compatibility, document features in README and CHANGELOG, then package for distribution. Marketplace readiness requires adherence to semantic versioning and consistent metadata structure.

Do I need to specify engine compatibility in my plugin configuration?

Yes. plugin.json must declare Claude Code engine compatibility to ensure your plugin installs correctly on target versions. This prevents installation failures and ensures users receive plugins matching their runtime environment.

How do optional MCP and dependency integrations work in plugins?

Plugins support optional MCP server integrations and external dependencies declared in plugin.json. These integrations extend plugin capabilities while keeping the core toolkit self-contained, allowing users to opt into advanced features as needed.