From ai-toolkit-dev
Use when authoring, publishing, or composing Claude Code plugin marketplaces. Covers `marketplace.json` schema and field reference, the five plugin source types (relative path, github, url, git-subdir, npm), `pluginRoot`, `category`, `tags`, `keywords`, `strict` mode, hosting and ref/sha pinning, version resolution, release channels, listing external plugins as a catalogue or plugin catalog, recommending marketplaces via `extraKnownMarketplaces`, and cross-marketplace dependencies via `allowCrossMarketplaceDependenciesOn`. Triggers on "create marketplace", "publish marketplace", "register a marketplace", "host a marketplace", "marketplace.json", "marketplace structure", "add plugin to marketplace", "share plugins with my team", "list someone else's plugin in my marketplace", "combine multiple marketplaces", "cross-marketplace dependency", "release channels", "stable vs latest plugin".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-toolkit-dev:marketplaceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A **marketplace** is a catalogue of plugins. It's a single JSON file (`.claude-plugin/marketplace.json`) at the root of a git repo, served as a static URL, or kept on a local path. Users add the marketplace once; afterwards every plugin in it is installable by `name@marketplace`.
A marketplace is a catalogue of plugins. It's a single JSON file (.claude-plugin/marketplace.json) at the root of a git repo, served as a static URL, or kept on a local path. Users add the marketplace once; afterwards every plugin in it is installable by name@marketplace.
name. The source field tells Claude Code how to fetch each one. Five source forms exist (string, github, url, git-subdir, npm).github, url, git-subdir) share the same pinning fields: ref? (branch/tag) and sha? (exact commit).allowCrossMarketplaceDependenciesOn.metadata.pluginRoot).| If the user wants to… | Read |
|---|---|
Look up a field name, source-type schema, or strict/version semantics | references/schema.md |
| Build a new marketplace from scratch — pick a layout, write the file, validate | references/setup.md |
| Ship a marketplace — host it, pin plugin versions, set up release channels, manage cache | references/publishing.md |
| Compose marketplaces — list third-party plugins, recommend other marketplaces, allow cross-marketplace deps, build a "merger" marketplace | references/referencing.md |
Full, valid marketplace.json files in examples/ — copy and adapt:
| File | Pattern |
|---|---|
minimal.json | Smallest valid marketplace |
dogfood.json | Self-hosted, plugins in same repo with pluginRoot |
catalogue.json | Third-party listings; one of every source type |
release-channels.json | Two marketplaces pointing at stable vs latest refs |
cross-marketplace-deps.json | allowCrossMarketplaceDependenciesOn opt-in |
team-recommendations.json | .claude/settings.json snippet (not a marketplace file) showing extraKnownMarketplaces |
inline-plugin.json | Marketplace entry that declares components inline (strict: false) |
plugin.json → use the plugin-dev skill.skill-creator skill.plugin-dev covers that. This skill covers the publisher side.Provides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.
npx claudepluginhub sidhanthapoddar99/sids-plugin-marketplace --plugin ai-toolkit-dev