marketplace-structure

Create and maintain Claude plugin marketplaces with marketplace.json manifests.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sjnims/plugin-dev --skill marketplace-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: marketplace-structure
Source: https://github.com/sjnims/plugin-dev/tree/main/plugins/plugin-dev/skills/marketplace-structure
Command: npx skills add https://github.com/sjnims/plugin-dev --skill marketplace-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

A marketplace organizes plugins for centralized discovery, version management, and distribution. This skill guides creating a marketplace manifest, defining ownership, and organizing plugin entries with optional metadata and sources.

Core Features & Use Cases

  • Marketplace manifest: Create and maintain .claude-plugin/marketplace.json with required fields and optional metadata.
  • Plugin entries: Define per-plugin metadata, sources (relative, GitHub, or URL), and optional fields like version, author, and categories.
  • Distribution strategies: Outline hosting options (GitHub, GitLab, local directories) and environment-specific marketplaces.

Quick Start

Initialize a small marketplace by creating a marketplace.json at .claude-plugin/marketplace.json and add a minimal plugin entry.

Frequently Asked Questions about marketplace-structure

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

FAQPage Schema
How do I create a marketplace for Claude plugins?▼

Create a marketplace by setting up a marketplace.json file at `.claude-plugin/marketplace.json` with required fields like owner and plugin entries. Define each plugin's metadata, sources (relative paths, GitHub, or Git URLs), and optional fields such as version and author to organize and distribute plugins centrally.

What is marketplace.json and what schema does it require?▼

Marketplace.json is a manifest file that defines your plugin marketplace structure. It requires validation against a defined schema, including owner and metadata fields, and supports both strict and non-strict validation modes to accommodate different distribution needs and source configurations.

Can I host plugins from multiple sources in one marketplace?▼

Yes, marketplace.json supports multiple source types for plugins: relative paths for local plugins, GitHub repositories, and Git URLs for remote sources. This flexibility lets you aggregate plugins from different origins into a single, centralized marketplace.

How do I configure plugin metadata and ownership in a marketplace?▼

Define per-plugin metadata including author, version, and categories in your marketplace.json entries. Set marketplace-level ownership fields to establish accountability. Both owner and metadata fields are required, with optional fields letting you add richer context for each plugin.

What are the differences between strict and non-strict marketplace validation modes?▼

Strict mode enforces all schema requirements rigorously, while non-strict mode allows more flexible configurations. Choose based on your distribution strategy—strict ensures compliance, non-strict accommodates varied plugin sources and organizational needs.

What workflows does a marketplace support after setup?▼

Marketplaces support installation, update, and validation workflows. After creating your manifest, users can discover and install plugins, receive updates from configured sources, and validate marketplace integrity against the schema.