Creating and Editing Claude Plugins

Guides developers in creating and editing Claude Code plugins with manifest configuration and component organization.

2|1|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/bbrowning/bbrowning-claude-marketplace --skill creating-and-editing-claude-plugins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Creating and Editing Claude Plugins
Source: https://github.com/bbrowning/bbrowning-claude-marketplace/tree/main/claude-builder/skills/plugin-builder
Command: npx skills add https://github.com/bbrowning/bbrowning-claude-marketplace --skill creating-and-editing-claude-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Developers need to extend Claude Code's functionality with custom commands, agents, and skills, and share these capabilities across projects or teams. This Skill provides the definitive guide to building robust, shareable plugins, allowing you to automate complex workflows and save time.

Core Features & Use Cases

  • Plugin Structure & Manifest: Learn to define your plugin's metadata and component locations using plugin.json for seamless integration and easy discovery.
  • Component Integration: Integrate custom slash commands, agents, skills, event hooks, and MCP servers into a cohesive plugin package, extending Claude's capabilities.
  • Version Control & Distribution: Master semantic versioning and best practices for testing, debugging, and sharing your plugins via marketplaces or direct installation, ensuring reliable deployment.

Quick Start

"I want to create a new Claude plugin. Guide me through the initial setup, including the plugin.json manifest and adding a basic skill."

Frequently Asked Questions about Creating and Editing Claude Plugins

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

FAQPage Schema
How do I create a Claude plugin with a plugin.json manifest?

Creating a Claude plugin starts with defining a plugin.json manifest that specifies metadata, component locations, and versioning. This file enables seamless integration of custom commands, skills, agents, and MCP servers into Claude Code, making your extensions discoverable and installable across projects.

What's the correct directory structure and layout for organizing plugin components?

Plugin components—commands, skills, agents, hooks, and MCP integrations—require a defined directory layout with proper path resolution and SKILL.md frontmatter conventions. Correct organization ensures Claude Code recognizes and loads each component reliably during plugin initialization.

How do I version and distribute Claude plugins to a marketplace?

Semantic versioning and distribution best practices ensure reliable plugin deployment across teams and marketplaces. Test and debug your plugin thoroughly before publishing, then share via marketplace or direct installation to enable other developers to extend their Claude Code environments.

Can I package multiple custom commands and agents into a single plugin?

Yes, Claude plugins support packaging multiple components—custom slash commands, agents, skills, event hooks, and MCP servers—into one cohesive plugin. Component integration through plugin.json enables you to extend Claude's functionality across multiple domains within a single distributable package.

What are the minimal requirements for a functioning Claude plugin?

A functioning Claude plugin requires a minimal plugin.json with correct metadata and component paths, proper directory structure, and SKILL.md documentation following established conventions. These functional requirements ensure your plugin integrates correctly and operates as intended in Claude Code environments.