create-claude-plugin

Create Claude Code plugins bundling skills, agents, commands, hooks, and MCP servers.

20|1|Updated Sep 30, 2025
One-click install
npx skills add https://github.com/ronnycoding/.claude --skill create-claude-plugin-ronnycoding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-claude-plugin
Source: https://github.com/ronnycoding/.claude/tree/main/skills/create-claude-plugin
Command: npx skills add https://github.com/ronnycoding/.claude --skill create-claude-plugin-ronnycoding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized way to bundle and distribute custom Claude Code skills, agents, commands, hooks, and MCP servers, enabling effortless team collaboration and community sharing.

Core Features & Use Cases

  • Unified Packaging: Combine multiple Claude Code extensions into a single, versioned plugin for easy distribution.
  • Team & Community Sharing: Share standardized workflows and specialized AI capabilities across your organization or with the broader community.
  • Simplified Installation: Users can install complex sets of tools with a single command, reducing setup time and complexity.
  • Use Case: Create a "Full Stack Development Toolkit" plugin that bundles a backend architect agent, an API design skill, and commands for scaffolding new components, then share it with your entire development team for consistent workflows.

Quick Start

Create a new plugin named my-devtools that bundles a code-reviewer agent and a test-automation skill, then configure its marketplace.json file.

Frequently Asked Questions about create-claude-plugin

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

FAQPage Schema
How do I package multiple Claude Code skills and agents into a single distributable plugin?

Package multiple Claude Code extensions by creating a plugin directory with a marketplace.json configuration file that specifies your skills, agents, commands, hooks, and MCP servers. This bundles them into a versioned plugin users can install with a single command, reducing setup complexity across teams or communities.

What should I include in a marketplace.json file for my Claude Code plugin?

The marketplace.json file defines your plugin's metadata, versioning, and component inventory—listing all bundled skills, agents, commands, hooks, and MCP servers. It enforces the plugin schema, enabling proper validation and marketplace deployment while ensuring users install the correct versions.

Can I share custom workflows and AI capabilities across my development team using plugins?

Yes. Plugins enable standardized distribution of custom Claude Code workflows and specialized capabilities to your entire team or community. Package your agents, skills, and commands once, then all team members install them consistently with a single command.

How do I test a Claude Code plugin locally before publishing to the marketplace?

Test locally by validating your plugin directory structure against the marketplace.json schema, verifying all bundled components load correctly, and running end-to-end workflows. Local testing ensures functionality before marketplace deployment.

What semantic versioning practices should I follow when publishing plugin updates?

Apply semantic versioning to your plugin releases—incrementing patch for bug fixes, minor for backward-compatible features, and major for breaking changes. This ensures users understand update impact and maintain compatibility across their installations.

What's the difference between publishing a plugin versus sharing individual skills?

Plugins bundle multiple interdependent components (skills, agents, commands, hooks, MCP servers) with unified versioning and configuration, enabling complex toolkits. Individual skills distribute single capabilities. Plugins streamline team workflows requiring coordinated multi-component installation.