cursor-upgrade-migration
Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines. Triggers on "upgrade cursor", "update cursor", "cursor migration", "cursor new version", "vs code to cursor", "cursor changelog".
71
88%
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 well-crafted skill description that clearly communicates specific capabilities (version upgrades, VS Code migration, settings transfer) and provides explicit trigger terms. The description is concise, uses third-person voice, and covers natural keyword variations users would employ. It serves as a strong example of an effective skill description.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Upgrade Cursor versions', 'migrate from VS Code', and 'transfer settings between machines'. These are clear, distinct capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (upgrade versions, migrate from VS Code, transfer settings) and 'when' with explicit trigger terms prefaced by 'Triggers on'. The trigger guidance is explicit and well-defined. | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'upgrade cursor', 'update cursor', 'cursor migration', 'cursor new version', 'vs code to cursor', 'cursor changelog'. Good coverage of variations including both 'upgrade' and 'update'. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche focused specifically on Cursor IDE upgrades and migrations. The trigger terms are highly specific to this domain and unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent workflow clarity and concrete commands for every migration/upgrade scenario. Its main weakness is length — the content tries to cover too many scenarios (upgrades, VS Code migration, machine transfer, breaking changes, enterprise) in a single file without progressive disclosure. Some sections like the extension table and enterprise considerations add bulk without proportional value.
Suggestions
Split the VS Code migration details, machine migration, and enterprise sections into separate referenced files to reduce the main SKILL.md to a concise overview with links.
Remove the extension marketplace table — Claude can infer that Microsoft-exclusive extensions won't be available; a one-line note about Open VSX vs Microsoft Marketplace suffices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some unnecessary content Claude would already know (e.g., explaining what auto-update does, the side-by-side section, the extension marketplace table with obvious entries). The enterprise section and some explanatory text could be trimmed significantly. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready commands for every scenario: brew upgrade, cp commands with exact paths, extension backup/restore one-liners, and specific file paths per OS. The checklists and bash scripts are directly executable. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with pre-upgrade and post-upgrade checklists serving as explicit validation checkpoints. The .cursorrules migration includes a verify-then-delete feedback loop. The upgrade workflow has a clear sequence: backup → upgrade → verify. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear headers, but it's a long monolithic file (~180 lines of content) with no bundle files to offload detail into. The extension marketplace table, enterprise considerations, and machine migration sections could be split into separate referenced files to keep the main skill lean. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
09b10d6
- 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.