review-plugin-submission
Audit a Cursor plugin for marketplace readiness. Use when validating manifests, component metadata, discovery paths, and submission quality before publishing.
58
66%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./create-plugin/skills/review-plugin-submission/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is well-structured with a clear 'what' and explicit 'when' clause, targeting a very specific niche (Cursor plugin marketplace auditing). Its main weakness is that the specific actions listed are somewhat categorical rather than deeply concrete, and the trigger terms could better cover natural user language variations like 'extension' or 'publish'.
Suggestions
Add more concrete actions such as 'validate package.json fields, check icon assets, verify README completeness' to increase specificity.
Include natural language variations users might say, such as 'Cursor extension', 'publish extension', 'store listing', or 'extension review' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor plugin marketplace readiness) and some actions (validating manifests, component metadata, discovery paths, submission quality), but these are somewhat abstract categories rather than deeply concrete actions like 'check version fields' or 'validate icon dimensions'. | 2 / 3 |
Completeness | Clearly answers both 'what' (audit a Cursor plugin for marketplace readiness) and 'when' (Use when validating manifests, component metadata, discovery paths, and submission quality before publishing). The 'Use when...' clause is explicit with trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Cursor plugin', 'marketplace', 'manifests', 'publishing', and 'submission quality', but misses common user variations like 'extension', 'Cursor extension', 'publish to marketplace', 'store listing', or 'package.json validation'. The terms are somewhat specialized and may not match how users naturally phrase requests. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Cursor plugin marketplace auditing is a narrow, well-defined domain that is unlikely to conflict with other skills. The combination of 'Cursor plugin', 'marketplace readiness', and 'manifests' creates a distinct trigger profile. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a well-structured audit checklist for Cursor plugin submissions with clear sections and specific file paths to verify. Its main weaknesses are the lack of executable validation commands/scripts and the absence of explicit error-handling or feedback loops when checks fail. The checklist section partially duplicates the workflow, and adding concrete tooling (e.g., a jq command to validate JSON, a regex for kebab-case) would significantly improve actionability.
Suggestions
Add concrete executable commands for key validation steps (e.g., `jq '.' .cursor-plugin/plugin.json` to validate JSON, a regex pattern like `^[a-z0-9]+(-[a-z0-9]+)*$` for kebab-case checking).
Add explicit failure handling: what should happen when a step fails (e.g., 'If manifest is missing, stop and report — do not proceed to component checks').
Remove or consolidate the Checklist section with the Workflow to eliminate redundancy, or differentiate them clearly (e.g., Checklist as a quick summary, Workflow as detailed steps).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient and doesn't over-explain basic concepts, but some sections could be tightened. For example, the checklist partially repeats information already covered in the workflow steps (e.g., manifest validity, broken references, missing frontmatter). | 2 / 3 |
Actionability | The skill provides specific file paths and field names to check (e.g., `.cursor-plugin/plugin.json`, kebab-case naming), which is helpful. However, it lacks concrete executable commands or code snippets for validation—there are no scripts, regex patterns for kebab-case validation, or JSON schema examples to make the checks copy-paste ready. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced into five numbered steps with sub-items, which is good. However, there are no explicit validation checkpoints or feedback loops—no guidance on what to do when a check fails, no error recovery steps, and no 'stop if X fails' gates between steps. | 2 / 3 |
Progressive Disclosure | For a skill of this size and scope (under 50 lines, single-purpose audit task), the content is well-organized into clear sections (Trigger, Workflow, Checklist, Output) without needing external references. The structure is easy to navigate and appropriately self-contained. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cursor/plugins
- Commit
b8f2564
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.