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.
85
81%
Does it follow best practices?
Impact
Pending
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 concisely covers specific capabilities, includes natural trigger terms, and explicitly states both what the skill does and when to use it. It uses proper third-person voice and targets a clear niche (Cursor plugin scaffolding) that minimizes conflict risk with other skills.
| 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', 'marketplace', 'multi-plugin repository'. These cover the terms a developer would naturally use when starting a plugin project. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets specifically Cursor plugin scaffolding with manifest and marketplace wiring. This is a clear niche unlikely to conflict with general code scaffolding or other IDE plugin 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 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 frontmatter templates, no marketplace.json snippet—which forces Claude to infer exact formats. The content would benefit significantly from adding template snippets and optionally splitting reference material into supporting files.
Suggestions
Add a concrete, copy-paste-ready example of a minimal plugin.json with all required and recommended fields filled in.
Include example frontmatter blocks for each component type (rules .mdc, skills SKILL.md, agents, commands) so Claude doesn't have to guess the exact format.
Add a sample marketplace.json entry snippet to make step 6 fully actionable.
Consider extracting the component frontmatter reference and plugin.json schema into a separate REFERENCE.md file to improve progressive disclosure.
| 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, frontmatter fields, and directory structures, but lacks any concrete code examples, template snippets, or copy-paste-ready plugin.json content. Claude would need to infer the exact JSON schema and frontmatter format rather than having executable examples to follow. | 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 ensuring manifest integrity. The process is unambiguous and well-structured for a generative (non-destructive) task. | 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 plugin.json schemas, frontmatter formats, and marketplace.json structure, these would benefit from separate reference files or at least inline examples rather than being left entirely implicit. | 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
7dd9fea
- 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.