Plugin Marketplace
Operational guide for building and maintaining Claude Code plugin marketplaces.
Activation Boundary
Use this skill only when the task involves plugin marketplace distribution:
- Creating or editing
.claude-plugin/marketplace.json
- Publishing a marketplace to GitHub, GitLab, Bitbucket, a git URL, or a local path
- Defining plugin source entries for marketplace installation
- Reviewing team marketplace allowlists or managed marketplace restrictions
- Debugging marketplace validation, install, update, or authentication failures
Do not use this skill for ordinary SKILL.md creation or skill quality review unless the user is also asking to distribute the skill through a plugin marketplace.
Core Rule
Inspect the target repository or marketplace folder before giving instructions.
Confirm:
- Existing
.claude-plugin/marketplace.json
- Existing plugin folders and
.claude-plugin/plugin.json manifests
- Whether sources are relative paths, GitHub repositories, git URLs, npm packages, or local paths
- Whether the marketplace is public, private, team-managed, or local-only
- Which command surface the user is using: Claude Code slash commands, CLI validation, or repository configuration
Do not invent marketplace fields. Follow the existing manifest shape or the schema reference.
Workflow
- Determine whether the user needs a marketplace catalog, a plugin entry, hosting guidance, or troubleshooting.
- Inspect existing marketplace files before editing.
- Use the schema reference for field names and required/optional structure.
- Use the source-types reference before choosing where plugin code is loaded from.
- Use hosting guidance when the task involves sharing, private repositories, or team policy.
- Use troubleshooting guidance only for observed validation, install, update, path, or auth failures.
Reference Navigation
- Marketplace setup:
references/plugin-marketplace-setup-overview.md
- Marketplace JSON schema:
references/plugin-marketplace-json-schema.md
- Plugin source types:
references/plugin-marketplace-source-types.md
- Hosting and distribution:
references/plugin-marketplace-hosting-distribution.md
- Errors and fixes:
references/plugin-marketplace-errors-and-fixes.md
Output Rule
For marketplace changes, produce the smallest valid manifest or config change that fits the repository's current distribution model.
For troubleshooting, report the observed failure, likely cause, verification step, and minimal fix.
1---2name: plugin-marketplace3description: Use when creating, reviewing, or troubleshooting Claude Code plugin marketplaces, marketplace.json files, plugin sources, hosting, team allowlists, or install/update failures.4license: MIT5---67# Plugin Marketplace89Operational guide for building and maintaining Claude Code plugin marketplaces.1011## Activation Boundary1213Use this skill only when the task involves plugin marketplace distribution:14- Creating or editing `.claude-plugin/marketplace.json`15- Publishing a marketplace to GitHub, GitLab, Bitbucket, a git URL, or a local path16- Defining plugin source entries for marketplace installation17- Reviewing team marketplace allowlists or managed marketplace restrictions18- Debugging marketplace validation, install, update, or authentication failures1920Do not use this skill for ordinary `SKILL.md` creation or skill quality review unless the user is also asking to distribute the skill through a plugin marketplace.2122## Core Rule2324Inspect the target repository or marketplace folder before giving instructions.2526Confirm:27- Existing `.claude-plugin/marketplace.json`28- Existing plugin folders and `.claude-plugin/plugin.json` manifests29- Whether sources are relative paths, GitHub repositories, git URLs, npm packages, or local paths30- Whether the marketplace is public, private, team-managed, or local-only31- Which command surface the user is using: Claude Code slash commands, CLI validation, or repository configuration3233Do not invent marketplace fields. Follow the existing manifest shape or the schema reference.3435## Workflow36371. Determine whether the user needs a marketplace catalog, a plugin entry, hosting guidance, or troubleshooting.382. Inspect existing marketplace files before editing.393. Use the schema reference for field names and required/optional structure.404. Use the source-types reference before choosing where plugin code is loaded from.415. Use hosting guidance when the task involves sharing, private repositories, or team policy.426. Use troubleshooting guidance only for observed validation, install, update, path, or auth failures.4344## Reference Navigation4546- Marketplace setup: `references/plugin-marketplace-setup-overview.md`47- Marketplace JSON schema: `references/plugin-marketplace-json-schema.md`48- Plugin source types: `references/plugin-marketplace-source-types.md`49- Hosting and distribution: `references/plugin-marketplace-hosting-distribution.md`50- Errors and fixes: `references/plugin-marketplace-errors-and-fixes.md`5152## Output Rule5354For marketplace changes, produce the smallest valid manifest or config change that fits the repository's current distribution model.5556For troubleshooting, report the observed failure, likely cause, verification step, and minimal fix.57
tamnguyendinh