Skip to main content
skill CX Codex

review-plugin-submission — Claude Code skill: audit a plugin before

Audits a Cursor plugin for marketplace readiness: manifest, component metadata, discovery paths, docs quality.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add cursor/plugins --skill review-plugin-submission -a claude-code
Open on GitHub

What review-plugin-submission does

The skill fires when a plugin is already built and needs a last check before release. It walks the sections, then returns a pass/fail report, a prioritized fix list and a submission recommendation.

Five blocks get checked. First the manifest at .cursor-plugin/plugin.json: the file exists, the name is lowercase kebab-case, and description, version, author and license stay coherent. Then component discovery — skills under skills/*/SKILL.md, rules in rules/ as .mdc or markdown, agents in agents/, commands in commands/, hooks in hooks/hooks.json, MCP config in mcp.json or via an mcpServers override. Metadata comes next: skills need name and description in frontmatter, agents and commands too. In a multi-plugin repo the plugin entry must exist in .cursor-plugin/marketplace.json, with source resolving to the plugin directory and names staying unique. The last block is README.md covering purpose, installation and component coverage.

The skill checks structure, not what your plugin actually does. If the repo has no marketplace.json, the registration step has nothing to work with — worth checking where you plan to publish.

What it helps with

  • check a plugin manifest before submitting to a marketplace
  • catch components that won't load because of wrong paths
  • verify frontmatter on skills, rules, agents and commands
  • confirm the plugin is registered in marketplace.json
  • get a prioritized fix list instead of walking files by hand

Example prompts for the agent

  • review my plugin before I submit it to the marketplace
  • run review-plugin-submission on the plugin repo
  • audit the plugin: manifest, components, README

How to install review-plugin-submission

1Skills CLI (Vercel)

npx skills add cursor/plugins --skill review-plugin-submission -a claude-code

2Manually: put the files in place

~/.claude/skills/review-plugin-submission/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/review-plugin-submission/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about review-plugin-submission

How do I install review-plugin-submission in Claude?

Run npx skills add cursor/plugins --skill review-plugin-submission -a claude-code. The skill file then sits at ~/.claude/skills/review-plugin-submission/SKILL.md.

What does review-plugin-submission do?

It checks a Cursor plugin for marketplace readiness: manifest, component metadata, discovery paths, marketplace registration and README quality. You get a pass/fail report by section plus a prioritized fix list.

Which files does the skill check?

.cursor-plugin/plugin.json, skills/*/SKILL.md, rules/, agents/, commands/, hooks/hooks.json, mcp.json, and .cursor-plugin/marketplace.json in multi-plugin repos.

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set45

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor