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.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 (scaffolds a Cursor plugin with specific artifacts) and when to use it (starting a new plugin or adding to a multi-plugin repo). It uses third person voice, includes natural trigger terms, and occupies a distinct niche that minimizes conflict risk.
| 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 scaffold with manifest, directories, marketplace wiring) and 'when' (explicitly states 'Use when starting a new plugin or adding a plugin to a multi-plugin repository'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords a user would say: 'Cursor plugin', 'scaffold', 'new plugin', 'manifest', 'marketplace', 'multi-plugin repository'. These cover the likely terms a developer would 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 |
Implementation
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 scaffolding Cursor plugins with clear sequencing and good organizational sections. Its main weakness is the lack of concrete, executable examples—no sample plugin.json, no template files, no example frontmatter—which forces Claude to guess at exact formats. The content is moderately concise but could trim some obvious metadata descriptions.
Suggestions
Add a concrete, copy-paste-ready example of a minimal plugin.json file with all required and recommended fields populated.
Include at least one example component file (e.g., a sample .mdc rule or SKILL.md) with valid frontmatter to make the guidance fully actionable.
Consider extracting the component frontmatter specifications into a reference file or providing a quick-reference table to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary detail that Claude could infer (e.g., explaining what kebab-case means, listing obvious metadata fields like 'name', 'version', 'description'). The guardrails section partially repeats information from the workflow. Could be tightened. | 2 / 3 |
Actionability | The workflow provides a clear sequence of steps and specifies file formats and frontmatter fields, but lacks any concrete code examples, actual file templates, or copy-paste-ready content for plugin.json, README.md, or component files. Claude would need to infer the exact structure of these files. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with logical ordering (validate → determine directory → create base files → populate manifest → create components → marketplace entry → validate paths). Step 7 serves as a validation checkpoint. The process is straightforward enough that explicit error-recovery loops aren't critical here since it's a generative/scaffolding task, not a destructive one. | 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 schema), example templates or a reference file for plugin.json schema would improve navigation. However, no bundle files exist to reference. | 2 / 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.