Name: create-plugin-scaffold
Rating: 70.39999999999999 (1 reviews)
Author: cursor

create-plugin-scaffold

Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

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 concise, well-organized instruction skill with a clear workflow and validation. Its weakest point is actionability: it names files and fields but omits ready-to-use templates.

Suggestions

Add a copy-paste-ready plugin.json skeleton with example values for the required and recommended fields.

Include example frontmatter blocks for at least a rule (.mdc) and a skill (SKILL.md) so the scaffolding is copy-paste ready.

Remove the repeated default-path mention (appears in Output Location, Workflow step 2, and Guardrails) to tighten redundancy.

Dimension	Reasoning	Score
Conciseness	Lean and well-sectioned with no concept-explaining padding; it assumes Claude's competence and every section earns its place.	3 / 3
Actionability	Concrete file paths and field lists are provided, but there are no copy-paste-ready plugin.json or frontmatter templates — key details for a scaffolding skill.	2 / 3
Workflow Clarity	A clear numbered sequence (steps 1-7) with an explicit validation step (relative/valid paths) and a validation-report deliverable.	3 / 3
Progressive Disclosure	Self-contained, single-purpose skill with well-organized sections and no nested external references — appropriate for its size.	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 strong description with concrete capabilities and an explicit Use-when trigger. The main weakness is narrow trigger-term coverage, which lacks common variations a user might say.

Suggestions

Broaden trigger terms to include natural variations like 'plugin scaffold', 'plugin template', 'boilerplate plugin', or 'marketplace plugin'.

Consider mentioning the component types directly in the description (rules, skills, agents) to improve trigger-term specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete deliverables — 'a valid manifest, component directories, and marketplace wiring' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (create scaffold with manifest/components/marketplace wiring) and when ('Use when starting a new plugin...').	3 / 3
Trigger Term Quality	'Use when starting a new plugin or adding a plugin to a multi-plugin repository' gives some natural keywords but misses common variations like 'plugin scaffold', 'plugin template', or 'marketplace plugin'.	2 / 3
Distinctiveness Conflict Risk	The Cursor plugin-scaffolding niche with marketplace/multi-plugin triggers is distinctive and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: 0452e08

Reviewed: 14 days ago

Table of Contents

Discovery Implementation Validation

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.