marketplace-builder
Create and configure Claude Code marketplaces and plugins. Use when the user wants to create a marketplace, publish plugins, set up team plugin distribution, or configure marketplace.json or plugin.json files. Triggers: create marketplace, publish plugin, plugin distribution, marketplace.json, plugin.json, team plugins, share plugins
Security Assessment
About marketplace-builder
The marketplace-builder skill provides structured guidance for creating and configuring Claude Code marketplaces and plugins. It addresses the complexity of organizing, distributing, and managing reusable components such as commands, agents, skills, hooks, and MCP servers. A key concept emphasized by this skill is the distinction between a marketplace and a plugin: a marketplace is a JSON catalog that indexes plugins, while a plugin is a packaged collection of components. Marketplaces do not host plugins; instead, they reference plugins that may reside in GitHub repositories, other git services, private repositories, or local directories. This separation enables flexible distribution models without coupling hosting and discovery.
The skill includes JSON schema references for marketplace.json, plugin.json, and team-level settings.json configurations. It documents supported source types, including GitHub repositories, generic Git URLs, directory paths, and relative paths. It also provides command-line references for adding, listing, updating, installing, enabling, disabling, and uninstalling plugins, along with structure validation using a validation command. Additionally, it outlines a six-phase workflow beginning with requirements gathering, where distribution type, plugin scope, target audience, and hosting environment are clarified before architectural decisions are made.
This skill is intended for developers, teams, and organizations that need to distribute Claude Code extensions in a structured and maintainable way. It supports scenarios ranging from personal plugin development to company-wide distribution and public community sharing. By following the documented architecture patterns and configuration formats, users can implement consistent plugin ecosystems tailored to their distribution strategy.
FAQ
What is the difference between a marketplace and a plugin?
A marketplace is a JSON catalog that indexes plugins, while a plugin is a packaged collection of components such as commands or agents. The marketplace does not host plugins; it references their locations.
Where can plugins be hosted?
Plugins can be hosted on GitHub, other git services using a Git URL, self-hosted git repositories, or local directories. The marketplace references these sources.
How are plugins enabled for a team?
Teams configure settings.json inside the .claude directory, specifying extraKnownMarketplaces and enabling plugins using the plugin-name@marketplace-name format.
What types of components can a plugin include?
A plugin can contain commands, agents, skills, hooks, MCP servers, or a combination of these components.
How can I validate a plugin structure?
You can run the validation command provided in the documentation to verify that the plugin structure is correct.
Install marketplace-builder
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mike-coulbourn/claude-vibes