CtrlK
BlogDocsLog inGet started
Tessl Logo

review-plugin-submission

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

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, token-efficient checklist-style skill with a clear sequenced workflow, but its verification criteria are sometimes vague and it lacks embedded validation checkpoints or feedback loops for what is effectively a batch audit.

Suggestions

Replace vague criteria ('metadata fields are coherent', 'clear guidance', 'scope is focused') with concrete pass/fail rules or a minimal valid-manifest example so checks are unambiguous.

Embed validation checkpoints in the workflow (e.g., 'if manifest fails to parse, report and halt') and add an explicit fix-then-revalidate feedback loop rather than only a final prioritized fix list.

Add one concrete example of a valid `.cursor-plugin/plugin.json` and a marketplace entry to make the discoverability and repository-integration checks copy-paste ready.

DimensionReasoningScore

Conciseness

Lean bullet structure with specific paths and no padding; it does not explain what a plugin or manifest is and assumes Claude's competence, so every token earns its place.

3 / 3

Actionability

Gives concrete file paths (`.cursor-plugin/plugin.json`, `skills/*/SKILL.md`, `hooks/hooks.json`) but criteria like 'metadata fields are coherent', 'clear guidance', and 'focused' are vague, and there are no executable commands or example manifests to make guidance copy-paste ready.

2 / 3

Workflow Clarity

Five steps are clearly sequenced and a separate Checklist exists, but no validation checkpoints are embedded in the workflow and there is no error-recovery feedback loop; per the batch-operation note this caps at 2.

2 / 3

Progressive Disclosure

Under 50 lines with no need for external references (none present) and well-organized into Trigger, Workflow, Checklist, and Output sections, which qualifies for 3 under the simple-skills note.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that states a concrete capability and an explicit 'Use when' trigger scoped to a distinct niche. It avoids fluff and over-claims while covering the relevant natural terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Audit a Cursor plugin for marketplace readiness' and 'validating manifests, component metadata, discovery paths, and submission quality' — rather than vague language.

3 / 3

Completeness

Explicitly states what ('Audit a Cursor plugin for marketplace readiness') and when ('Use when validating manifests, component metadata, discovery paths, and submission quality before publishing') with an explicit 'Use when' trigger.

3 / 3

Trigger Term Quality

Covers natural domain terms a plugin submitter would say ('manifests', 'component metadata', 'submission quality', 'publishing', 'marketplace readiness'); 'discovery paths' is slightly jargon-y but the set is well-covered.

3 / 3

Distinctiveness Conflict Risk

The 'Cursor plugin' / 'marketplace readiness' / 'before publishing' niche is narrow and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cursor/plugins
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.