Review Plugin Submission

This runs through a full pre-flight check before you publish a Cursor plugin to the marketplace. It validates your manifest structure, confirms all your skills, rules, agents, and commands are discoverable in their expected directories, checks that frontmatter exists where it should, and makes sure your README actually explains what the plugin does. The output is a pass/fail breakdown with a prioritized fix list, which beats hunting through folders manually wondering why your plugin isn't loading. Most useful right before you hit submit, or when inheriting someone else's plugin and needing to know what's broken.

skills.sh installs: 1.2K
GitHub stars: 15.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cursor/plugins --skill review-plugin-submission --agent claude-code

Installs into .claude/skills of the current project.

Files

Review plugin submission

Trigger

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

Workflow

Verify manifest validity:
- .cursor-plugin/plugin.json exists
- name is valid lowercase kebab-case
- metadata fields are coherent (description, version, author, license)
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)
Verify component metadata:
- Skills include name and description frontmatter
- Rules include valid frontmatter and clear guidance
- Agents and commands include name and description
Verify repository integration:
- For marketplace repos, plugin entry exists in .cursor-plugin/marketplace.json
- source resolves to plugin directory and names are unique
Verify documentation quality:
- README.md states purpose, installation, and component coverage
- optional logo path is valid and repository-hosted