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

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A compact, cleanly structured audit skill that sequences its checks clearly and stays token-efficient. Its main gap is actionability: it tells Claude what to verify but rarely how, lacking commands or examples that make the checks executable.

Suggestions

Add concrete verification helpers, e.g. a regex or rule for 'valid lowercase kebab-case' names and a jq snippet for parsing and validating plugin.json.

Include a brief valid/invalid example for at least one check (e.g. a correct vs malformed manifest) so Claude can pattern-match rather than infer.

Optionally fold the Checklist into the Workflow steps or note the relationship, since the two currently overlap without cross-reference.

DimensionReasoningScore

Conciseness

The body is lean and well-organized into Trigger/Workflow/Checklist/Output with no padding and no explanation of concepts Claude already knows, so every section earns its place.

3 / 3

Actionability

It names concrete targets (e.g. '.cursor-plugin/plugin.json', 'skills/*/SKILL.md', 'hooks/hooks.json') and specific field checks, but gives no executable commands, validation regexes, or valid/invalid examples, so the guidance is concrete but incomplete on how to actually perform each check.

2 / 3

Workflow Clarity

A clear five-step sequence with sub-bullets plus a dedicated Checklist and Output section provides explicit verification structure; as an audit skill the workflow is itself the validation, and the prioritized fix list supplies the error-recovery feedback path.

3 / 3

Progressive Disclosure

At well under 50 lines with no need for external references, the well-organized sections (Trigger, Workflow, Checklist, Output) meet the simple-skill allowance for a top progressive-disclosure score.

3 / 3

Total

11

/

12

Passed

Description

85%

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 tight, well-constructed description that pairs a concrete capability statement with an explicit 'Use when' trigger and a distinct niche. It is held back only by trigger phrasing that is more technical than colloquial.

Suggestions

Soften jargon in the trigger with natural phrasings users actually say, e.g. 'Use when publishing or submitting a Cursor plugin to the marketplace, or doing a final review before release.'

Add common-sense synonyms like 'plugin review', 'marketplace submission', or 'plugin checklist' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions — 'validating manifests, component metadata, discovery paths, and submission quality' — matching the anchor for listing several specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly states what it does ('Audit a Cursor plugin for marketplace readiness') and when to use it via an explicit 'Use when ... before publishing' clause, satisfying both the what and the when.

3 / 3

Trigger Term Quality

Includes relevant triggers like 'validating manifests', 'submission quality', 'before publishing', but leans on technical jargon ('discovery paths', 'component metadata') rather than the full range of natural phrasings a user might say, so it stops short of the top anchor.

2 / 3

Distinctiveness Conflict Risk

The narrow scope of 'Cursor plugin for marketplace readiness' with publish/submission triggers carves a clear niche that is unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.