# claude-marketplace-registration Plugins must be registered in marketplace.json *Formerly known as `marketplace-registration`. The legacy name still works in configs, `--rule`/`--skip-rule`, suppression comments, and baselines.* | | | |---|---| | **Severity** | error (auto) | | **Autofix** | auto | | **Since** | v0.1.0 | | **Repo Types** | marketplace | | **Category** | [Claude Code](claude.md) | ## Why A plugin that exists in the repository but is not registered in `marketplace.json` is invisible to marketplace tooling — users cannot discover or install it through the standard workflow. This requirement applies to Claude plugins. Hosting a Claude marketplace beside a root Codex plugin does not require registering that Codex plugin in the Claude catalog. The catalog declares its entries as Claude plugins, not its parent directory. ## Examples **Bad:** A `deploy-plugin/` directory exists but `marketplace.json` has no entry for it. **Good:** ```json { "plugins": [ { "name": "deploy-plugin", "path": "deploy-plugin/" } ] } ``` ## How to fix Add the plugin to the `plugins` array in `marketplace.json` with at least its `name` and `path`. `skillsaw fix` can append the missing entry, except when the violation is reported without the fixable marker because the file cannot be rewritten safely: `marketplace.json` is not valid JSON, its root is not an object, `plugins` is not an array, or the plugin lives outside `metadata.pluginRoot` (no valid relative `source` exists — move the plugin under the plugin root or adjust `pluginRoot`). ## Configuration ```yaml rules: claude-marketplace-registration: enabled: auto # true | false | auto severity: error ``` *Run `skillsaw explain claude-marketplace-registration` to see this documentation and the rule's effective configuration in your terminal.*