Name: create-plugin-scaffold
Rating: 68 (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

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

62%

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 workflow for creating Cursor plugin scaffolds with clear sequencing and good organizational sections. Its main weakness is the lack of concrete, executable examples—no sample plugin.json, no example .mdc frontmatter, no marketplace.json template—which forces Claude to guess at exact formats. The content would benefit significantly from adding copy-paste ready templates for the key artifacts it instructs Claude to create.

Suggestions

Add a concrete example of a complete plugin.json with all recommended fields filled in, so Claude knows the exact schema and format.

Include example frontmatter blocks for each component type (rules .mdc, skills SKILL.md, agents, commands) showing valid YAML frontmatter.

Add a sample marketplace.json entry showing the expected structure with all fields.

Consider extracting detailed component specifications into a referenced file (e.g., COMPONENTS.md) to keep the main skill lean while providing depth.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary structure like the 'Required Inputs' section that restates what Claude would naturally gather from conversation. The guardrails section partially repeats guidance already implied by the workflow. However, it avoids explaining basic concepts Claude already knows.	2 / 3
Actionability	The workflow provides clear steps and specifies file names, paths, and frontmatter fields, but lacks concrete executable examples. There are no actual code snippets showing what a valid plugin.json looks like, what .mdc frontmatter looks like, or what a marketplace.json entry contains. These would be copy-paste ready templates that significantly improve actionability.	2 / 3
Workflow Clarity	The 7-step workflow is clearly sequenced with logical ordering (validate name → determine directory → create base files → populate manifest → create components → marketplace wiring → validate paths). Step 7 serves as a validation checkpoint for manifest integrity. The output section includes a validation report requirement. For a scaffolding task (non-destructive, creating new files), this level of workflow clarity is appropriate.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections (Trigger, Required Inputs, Workflow, Guardrails, Output), but everything is inline in a single file with no references to supporting materials. Given the complexity of the topic (multiple component types, marketplace wiring, manifest schemas), concrete examples of plugin.json, marketplace.json, and component frontmatter would benefit from being in referenced files or at least included as inline examples.	2 / 3
	Total	9 / 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.

This is a strong, well-crafted description that clearly communicates what the skill does and when to use it. It uses specific, concrete terminology relevant to Cursor plugin development and includes an explicit 'Use when' clause with natural trigger scenarios. The description is concise, uses third person voice, and occupies a distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Create a new Cursor plugin scaffold', 'valid manifest', 'component directories', and 'marketplace wiring'. These are concrete, actionable outputs.	3 / 3
Completeness	Clearly answers both what ('Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring') and when ('Use when starting a new plugin or adding a plugin to a multi-plugin repository') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'Cursor plugin', 'scaffold', 'new plugin', 'manifest', 'multi-plugin repository', 'marketplace'. These cover the terms a developer would naturally use when starting a plugin project.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — 'Cursor plugin scaffold' is a very specific niche. The combination of Cursor, plugin, scaffold, manifest, and marketplace wiring makes it unlikely to conflict with other skills.	3 / 3
	Total	12 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: cfd81b3

Reviewed: 3 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.