maintaining-a-marketplace_skill

This skill helps maintain a Claude Code Plugin Marketplace by ensuring marketplace.json and plugin.json stay in sync across versions and changelogs.

Python

128

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ed3dai/ed3d-plugins --skill maintaining-a-marketplace

SKILL.md7.5 KB

Overview

This skill helps create, release, and maintain a Claude Code Plugin Marketplace with checks to prevent version and metadata drift. It documents the marketplace.json schema, source formats, release checklist, changelog conventions, and validation steps. Use it to keep plugin manifests, marketplace catalog, and changelog synchronized for reliable installs.

How this skill works

The skill inspects .claude-plugin/marketplace.json and each plugin’s .claude-plugin/plugin.json to verify required fields and matching version strings. It guides the ordered release workflow: bump plugin.json, update marketplace.json, add changelog entry, validate, then commit and push. It also validates schema fields, source formats, and common pitfalls that break installation or auto-update behavior.

When to use it

Creating a new marketplace repository from scratch
Releasing or tagging a new plugin version
Adding a plugin entry to an existing marketplace
Auditing or troubleshooting plugin install failures
Ensuring changelog, plugin.json, and marketplace.json stay in sync

Best practices

Always include $schema in marketplace.json for validation tooling
Bump plugin.json first, then update marketplace.json and CHANGELOG.md in a single commit
Run claude plugin validate . (or /plugin validate .) before pushing
Use explicit source formats (relative paths for git-based local repos, github/url objects for remote)
Write precise changelog entries that name specific skills or agents changed

Example use cases

Prepare a release: bump plugin version, update marketplace entry, add changelog, validate, commit and push
Add an internal plugin to the company marketplace using a relative source path and a changelog entry
Audit a marketplace to find version drift between plugin.json, marketplace.json, and the changelog
Configure team repo settings so colleagues are prompted to install recommended plugins via .claude/settings.json
Set up private repo auto-updates by providing appropriate environment tokens for GitHub/GitLab/Bitbucket

FAQ

Required: name (kebab-case), owner object with name and email, metadata.version, metadata.pluginRoot, and a plugins array with each plugin name and source.

How do I verify versions match across files?

Confirm plugins/<name>/.claude-plugin/plugin.json version, .claude-plugin/marketplace.json plugin entry version, and CHANGELOG.md entry header all show the same version string.

When should I use relative source paths vs remote sources?

Use relative paths for monorepo or git-based marketplace adds. Use github or url source objects for external repositories or pinned refs.