MCPInstall

review-plugin-submission

Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.

Installs
1.2K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/cursor/plugins --skill review-plugin-submission
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads review-plugin-submission automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Review plugin submission

Trigger

A plugin is implemented and needs a final quality check before submission or release.

Workflow

  1. Verify manifest validity:
    • .cursor-plugin/plugin.json exists
    • name is valid lowercase kebab-case
    • metadata fields are coherent (description, version, author, license)
  2. Verify component discoverability:
    • Skills in skills/*/SKILL.md
    • Rules in rules/ as .mdc or markdown variants
    • Agents in agents/ markdown files
    • Commands in commands/ markdown or text files
    • Hooks in hooks/hooks.json
    • MCP config in mcp.json (or mcpServers override)
  3. Verify component metadata:
    • Skills include name and description frontmatter
    • Rules include valid frontmatter and clear guidance
    • Agents and commands include name and description
  4. Verify repository integration:
    • For marketplace repos, plugin entry exists in .cursor-plugin/marketplace.json
    • source resolves to plugin directory and names are unique
  5. Verify documentation quality:
    • README.md states purpose, installation, and component coverage
    • optional logo path is valid and repository-hosted

Checklist

  • Manifest exists and parses as valid JSON
  • All declared paths exist and are relative
  • No broken file references
  • No missing frontmatter on skills/rules/agents/commands
  • Plugin scope is clear and focused
  • Marketplace registration complete (if multi-plugin repo)

Output

  • Pass/fail report by section
  • Prioritized fix list
  • Final submission recommendation

FAQ

What does the review-plugin-submission skill do?

Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.

How do I install review-plugin-submission?

Run npx skills add https://github.com/cursor/plugins --skill review-plugin-submission in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/review-plugin-submission/ (personal) or .claude/skills/review-plugin-submission/ (project).

Which AI agents can use review-plugin-submission?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is review-plugin-submission safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains review-plugin-submission?

It is published by cursor in cursor/plugins. It has 1,181 recorded installs.

More from cursor/plugins

View all →

unslop

cursor/plugins

Cut AI tells from any writing.

Docs & Writing28.3K installs

Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.

deslop

cursor/plugins

Remove AI-generated code slop and clean up code style

9.4K installs

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

how

cursor/plugins

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.

blast-radius

cursor/plugins

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

Docs & Writing5.9K installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.