feat: validate marketplace.json using claude plugin validate

[glebedel]

Summary

Uses claude plugin validate . — a built-in CLI command in @anthropic-ai/claude-code — to validate the marketplace manifest in CI. No custom scripts or extra dependencies.

The workflow

```yaml

• name: Validate plugin manifests
  run: npx --yes @anthropic-ai/claude-code plugin validate .
  ```

That's it. Claude Code runs the exact same internal Zod schema validation and exits 1 on failure with clear error messages, e.g.:

```
✘ Found 2 errors:
❯ plugins.0.source: Invalid input
```

Previous approach

PR originally used a hand-rolled Zod schema reverse-engineered from cli.js. Replaced with the official CLI command after discovering claude plugin validate exists — no need to maintain a schema copy.

Test plan

• claude plugin validate . passes locally on current manifests
• Verified bad source "." exits 1 with plugins.0.source: Invalid input
• CI passes on this PR

🤖 Generated with Claude Code

[cubic-dev-ai]

1 issue found across 5 files

Prompt for AI agents (all issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/validate-marketplace.js">

<violation number="1" location="scripts/validate-marketplace.js:11">
P2: `new URL(...).pathname` produces URL-encoded or Windows-incompatible paths. This can make `resolve(ROOT, ...)` fail on Windows or when the repo path contains spaces. Use `fileURLToPath(new URL("..", import.meta.url))` instead, and import `fileURLToPath` from `url`.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}