Skip to content

@remotion/claude-code-plugin: Fix marketplace description placement - #10538

Open
JonnyBurger wants to merge 1 commit into
mainfrom
codex/fix-claude-marketplace-description
Open

@remotion/claude-code-plugin: Fix marketplace description placement#10538
JonnyBurger wants to merge 1 commit into
mainfrom
codex/fix-claude-marketplace-description

Conversation

@JonnyBurger

Copy link
Copy Markdown
Member

Summary

Remove the root-level description from the Claude Code marketplace manifest.

The plugin-specific description remains in plugins[0], avoiding validation failures in the community marketplace while preserving the listing description.

Testing

  • bun run build
  • bun run stylecheck
  • Claude Code plugin manifest and package tests

@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
bugs Ready Ready Preview Aug 18, 2026 4:02pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
remotion Skipped Skipped Aug 18, 2026 4:02pm

Request Review

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ No critical issues — one diagnostic detail worth double-checking (inline on the deleted line).

Reviewed changes

Reviewed the full diff of this PR: a single-line deletion in the Claude Code plugin marketplace manifest.

  • Removes the root-level description from .claude-plugin/marketplace.json

ℹ️ If the manifest really was rejected, $schema is the more suspicious artifact — and it's left untouched

The PR explains the deletion as avoiding "validation failures in the community marketplace", but the manifest's $schema reference — https://json.schemastore.org/claude-code-plugin-marketplace.json — returns 404 today and never existed in the schemastore catalog (the real schema is claude-code-marketplace.json). If a validator rejected this manifest, that broken reference is the likelier in-file culprit. The deletion is harmless either way, so nothing blocks merging here — but confirming the actual rejection message (and optionally pointing $schema at the real schema) would get closer to the true root cause.

Pullfrog  | Fix all ➔Fix 👍s ➔View workflow run | Using DeepSeek Flash (free via Pullfrog for OSS) | 𝕏

"name": "Remotion",
"email": "hi@remotion.dev"
},
"description": "Plugins for building programmatic videos with Remotion",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the official Claude Code marketplace schema and docs, a root-level description is a documented optional marketplace field — so per public documentation this deletion isn't what validation requires, and it drops the marketplace-level description shown to users browsing /plugin marketplace. If the community submission genuinely rejected something, it would help to share the exact error and confirm the true root cause.

Technical details
# Root-level `description` is valid marketplace metadata

The official schema (https://json.schemastore.org/claude-code-marketplace.json) declares a top-level `description` property ("Human-readable description of this marketplace") with no root-level `additionalProperties: false`, so schema validation accepts the field. The Claude Code docs list `description` as an optional marketplace field (https://code.claude.com/docs/en/plugin-marketplaces).

## Affected sites
- `packages/claude-code-plugin/.claude-plugin/marketplace.json` — root-level `description` removed

## Observations for the human
- The manifest's `$schema` value (`claude-code-plugin-marketplace.json`) never existed in schemastore and 404s today; the matching schema is `claude-code-marketplace.json`. If an external validator rejected the manifest, that broken reference — untouched by this PR — is the more likely culprit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant