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".

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable, well-sequenced content with good validation checkpoints, but it underuses progressive disclosure — the body replicates material already in orphaned reference files rather than pointing to them.

Suggestions

Replace the inline upgrade/migration/checklist sections with concise overviews that link to the matching reference files (upgrade-methods.md, vs-code-to-cursor-migration.md, pre-upgrade-checklist.md, troubleshooting-upgrades.md, migration-between-machines.md) so SKILL.md acts as a hub.

Add explicit per-section pointers (e.g. 'See [references/troubleshooting-upgrades.md]') so the existing bundle files are discoverable instead of orphaned.

Trim explanatory prose Claude can infer (e.g. the side-by-side separate-directories list) and remove commands already covered in references to cut token cost.

Dimension	Reasoning	Score
Conciseness	Mostly lean commands and checklists, but the ~180-line body duplicates material already present in the reference files and includes some explanatory prose (e.g. the side-by-side directory list) Claude could infer.	2 / 3
Actionability	Packed with executable bash commands, exact config paths, copy-paste migration snippets, and a concrete extension-compatibility table — copy-paste ready.	3 / 3
Workflow Clarity	Clear sequenced workflows with a pre-upgrade backup checklist and a post-upgrade verification checklist; the .cursorrules migration includes a test-before-delete validation step.	3 / 3
Progressive Disclosure	Seven reference files exist but the body never links to them; content that belongs in those references (upgrade methods, VS Code migration, checklists, troubleshooting) is duplicated inline instead of being split out and signaled.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description with concrete actions, natural trigger terms, and explicit when-guidance in third person. No fluff or over-claims, and a clearly distinct niche.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines' — rather than vague language.	3 / 3
Completeness	Answers both what (upgrade/migrate/transfer) and when via an explicit 'Triggers on ...' clause equivalent to a 'Use when' trigger.	3 / 3
Trigger Term Quality	Includes six natural phrases a user would actually say ('upgrade cursor', 'update cursor', 'cursor migration', 'cursor new version', 'vs code to cursor', 'cursor changelog').	3 / 3
Distinctiveness Conflict Risk	A narrow Cursor-IDE-specific niche with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/cursor-pack/skills/cursor-upgrade-migration/SKILL.md
Commit: c4eafaf

Reviewed: 1 day 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.