review-plugin-submission

Audit Cursor plugin manifests and metadata for marketplace submission readiness.

2.6k|204|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill review-plugin-submission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-plugin-submission
Source: https://github.com/cursor/plugins/tree/main/create-plugin/skills/review-plugin-submission
Command: npx skills add https://github.com/cursor/plugins --skill review-plugin-submission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a Cursor plugin to ensure marketplace readiness by validating manifests, metadata, and submission quality before publishing.

Core Features & Use Cases

  • Validate plugin manifests and metadata coherence across components.
  • Verify component discoverability (skills, rules, agents, commands, hooks) and repository integration.
  • Produce a pass/fail readiness report with prioritized fixes.

Quick Start

Run this skill against a ready plugin directory to generate a submission readiness report.

Frequently Asked Questions about review-plugin-submission

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a Cursor plugin manifest before marketplace submission?

Validate a Cursor plugin manifest by auditing the plugin directory to verify manifest structure, metadata coherence, and component discoverability, producing a pass/fail readiness report with prioritized fixes before marketplace publishing.

What is plugin marketplace readiness and how does discovery validation work?

Marketplace readiness verifies a plugin passes manifest validity, metadata coherence, and discoverability checks. Discovery validation confirms that skills, rules, agents, commands, and MCP configurations are correctly integrated and discoverable within the repository.

Can I audit MCP configurations and agent metadata in a Cursor plugin repository?

Yes, auditing MCP configurations and agent metadata in a Cursor plugin repository verifies their structural integrity, metadata coherence, and repository integration, ensuring all components meet marketplace submission standards.

What's the best way to check plugin submission quality before publishing?

Run an automated readiness audit against the plugin directory to check submission quality. This validates manifests, verifies component discoverability, and produces a prioritized pass/fail report covering documentation and metadata gaps before publishing.

Does the plugin audit work with repositories containing multiple skills and rules?

Yes, the audit applies to marketplace repositories containing multiple components, validating discoverability and metadata coherence across all integrated skills, rules, agents, commands, and hooks within the repository structure.

Why does my plugin fail manifest validation during marketplace submission?

Plugins fail manifest validation due to incoherent metadata, missing component definitions, or poor repository integration. An audit identifies these specific issues by checking manifest validity and producing a report with prioritized fixes.