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".
89
88%
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 well-crafted skill description that clearly defines its scope around Cursor IDE management tasks. It provides specific actions, explicit trigger terms covering natural user language variations, and occupies a distinct niche that minimizes conflict risk with other skills.
| 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' (explicit trigger terms prefaced with '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 management tasks. The trigger terms are highly specific to Cursor and unlikely to conflict with other skills. 'vs code to cursor' clearly differentiates from general VS Code 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—pre/post upgrade checklists, clear migration steps, and validation checkpoints throughout. The main weakness is that it's somewhat long for a single SKILL.md file, with some sections (extension marketplace table, enterprise considerations) that could be trimmed or split into separate files. The actionability is strong with platform-specific commands and concrete paths.
Suggestions
Consider splitting VS Code migration details and machine transfer instructions into separate referenced files (e.g., VSCODE_MIGRATION.md, MACHINE_TRANSFER.md) to keep SKILL.md as a concise overview.
Trim the extension marketplace table—a brief note that Cursor uses Open VSX and Microsoft-exclusive extensions aren't available would suffice, saving ~15 lines.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some content that could be trimmed—the extension marketplace table with repeated 'Available (Open VSX)' entries is verbose, the enterprise considerations section is somewhat generic, and the side-by-side running note is low-value. However, most content is practical and not overly explanatory. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready commands for every scenario: brew upgrade, cp commands with full paths, extension backup/restore one-liners, and specific UI navigation paths (Cmd+Shift+P, Help > About). The checklists are specific and testable. | 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 has a clear sequence with a verification step (type @Cursor Rules) before the destructive delete step. The upgrade workflow follows a logical backup → upgrade → verify pattern. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, but it's a long monolithic file (~150+ lines of substantive content) that could benefit from splitting detailed sections (VS Code migration, machine transfer) into separate referenced files. The Resources section at the end provides external links but no internal file references for progressive disclosure. | 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
c8a915c
- 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.