marketplace-builder

Create marketplace.json and plugin.json manifests from user requirements and repository inputs.

37|4|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/mike-coulbourn/claude-vibes --skill marketplace-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marketplace-builder
Source: https://github.com/mike-coulbourn/claude-vibes/tree/main/plugins/vibes/skills/marketplace-builder
Command: npx skills add https://github.com/mike-coulbourn/claude-vibes --skill marketplace-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of creating, configuring, and distributing Claude Code marketplaces and plugins. It eliminates confusion around marketplace architecture, JSON schemas, and distribution strategies, enabling seamless sharing of AI tools across teams or publicly.

Core Features & Use Cases

  • Marketplace & Plugin Creation: Guides you through setting up marketplace.json and plugin.json for single or multi-plugin architectures.
  • Distribution Strategies: Learn how to distribute plugins for personal use, team collaboration via Git, or public communities.
  • Validation & Testing: Provides steps to validate JSON syntax, test marketplace addition, and verify plugin functionality.
  • Use Case: Your team has developed several internal Claude plugins and needs a centralized way to distribute and manage them. This skill helps you design a monorepo marketplace, configure the necessary JSON files, and set up team-wide distribution via .claude/settings.json.

Quick Start

Ask the marketplace-builder to help you create a new marketplace for your team's internal Claude plugins.

Frequently Asked Questions about marketplace-builder

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

FAQPage Schema
How do I create a marketplace.json to distribute Claude plugins across my team?

A marketplace.json file defines your plugin collection and distribution settings. Create it by specifying plugin sources (GitHub repos, Git URLs, or local directories), metadata, and team access rules. This Skill guides you through the configuration to enable seamless plugin sharing via Claude Code's marketplace system.

What's the difference between a single-plugin and multi-plugin marketplace setup?

A single-plugin marketplace distributes one plugin; a multi-plugin marketplace centralizes several plugins in one configuration. Multi-plugin setups work best in monorepos or when managing related tools as a collection. This Skill helps you choose the right architecture and configure plugin.json manifests for either approach.

Can I distribute Claude plugins to my team via Git without hosting them publicly?

Yes. You can distribute plugins privately by referencing Git repositories or local directories in your marketplace.json, then share the marketplace configuration through your team's .claude/settings.json. This Skill handles the full setup for private, team-wide distribution across multiple environments.

How do I validate that my plugin.json and marketplace.json follow the correct schema?

This Skill provides validation steps to check JSON syntax and schema compliance for both files. It ensures your manifests conform to Claude Code's plugin structure requirements—including commands, agents, skills, hooks, and MCP specifications—before deployment.

Do I need to restructure my repository to create a marketplace?

No. This Skill supports GitHub, Git URLs, relative paths, and local directories as plugin sources, so it works with your existing monorepo or multi-repo layout. It enforces the plugin structure internally without requiring you to reorganize your codebase.

What happens after I set up my marketplace—how do I test it before rolling out to the team?

After configuration, this Skill provides steps to test marketplace addition in Claude Code and verify individual plugin functionality. Testing ensures your marketplace.json and plugin.json work correctly before you distribute them via team settings.