Skills

Marketplace Dev

Builds and maintains Claude Code plugin marketplaces: converts a skills repo to...

Install

npx skills add daymade/claude-code-skills --skill marketplace-dev -g -a claude-code -y
Category
AI and agents
Updated
3d ago
License
MIT
Context cost
Mediumabout 3,000 tokens
Runs scripts
Yes, review before use

What it does

Builds and maintains Claude Code plugin marketplaces: converts a skills repo to spec-valid marketplace.json, adds/updates plugin entries, and migrates skills into or between suites. Use for marketplace.json, plugin distribution, one-click install, or "put these skills in a suite". Not for repo health audits (use marketplace-health-check) or cache reconciliation (use skill-governance).

marketplace-dev

Convert a Claude Code skills repository into an official plugin marketplace so users can install skills via claude plugin marketplace add and get auto-updates.

Input: a repo with skills/ directories containing SKILL.md files. Output: .claude-plugin/marketplace.json + validated + installation-tested + PR-ready.

Route the task before editing

User intentRoute
Create marketplace support for a repo that does not have itFollow Phases 0, 4 below
Add or update an ordinary plugin entryFollow “Maintaining an existing marketplace,” then Phase 3
Consolidate standalone skills into a suite, create a suite from existing skills, move a skill between suites, or rename a skill while moving itRead references/suite_consolidation_workflow.md completely and follow it instead of the generic Phase 4 constraints
Reconcile installed caches after a merged suite migrationInvoke daymade-skill:skill-governance and use its post-migration workflow; do not mutate cache state here
Audit the whole repository across code, docs, security, PRs, issues, and manifest integrityInvoke marketplace-health-check:marketplace-health-check only when the user requested a broad health check; it is not a prerequisite for a targeted suite migration

Phase 0: Evidence Intake

Before editing an existing marketplace, collect evidence instead of relying on the default template:

  1. Read the current .claude-plugin/marketplace.json.
  2. Read this repo's marketplace rules (CLAUDE.md, README install section, changelog).
  3. Read official docs for marketplace/plugin path semantics.
  4. Use the current conversation as evidence. Mine earlier local Claude Code sessions only when the user explicitly asks for or approves that private source.
Read the whole SKILL.md on GitHub

More in AI and agents