Agent skill

Cursor Upgrade Migration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines.

MITAuto-check passedDevelopment

Install Cursor Upgrade Migration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-upgrade-migration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace cursor-upgrade-migration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/cursor-upgrade-migration .claude/skills/cursor-upgrade-migration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cursor-upgrade-migration
GitHub stars
2.8k
Token cost
~2.1k tokens
SKILL.md length
589 words
Files
8 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines.

  • Works in 4 steps: Inventory settings, extensions, rules,… → Test the target version with a pilot… → Document compatibility, performance, and… → …
  • Cursor migration
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 8 more sections
  • Calls cursor, brew and curl; reaches cursor.com and download.cursor.com

What it does

Cursor Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/errors.md`, `references/examples.md` and `references/migration-between-machines.md`). Compatibility notes: Designed for Claude Code

It sits in Development, covering Changelog and release notes. It works with Visual Studio Code. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Cursor migration
  • Cursor new version
  • Vs code to cursor
  • Cursor changelog

Example prompts

  • “upgrade cursor”
  • “update cursor”
  • “cursor migration”
  • “/cursor-upgrade-migration”

Requirements

  • Python 3
  • Docker
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(cmd:*)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Inventory settings, extensions, rules, integrations, and identity/privacy requirements.
  2. Test the target version with a pilot using non-sensitive workspaces and required workflows.
  3. Document compatibility, performance, and policy results before broader rollout.
  4. Roll back or pause on sign-in, privacy, extension, or workflow regression; retain evidence for follow-up.

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(cmd:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cursor
    • brew
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • cursor.com
    • download.cursor.com

    Also links to:

    • changelog.cursor.sh
    • docs.cursor.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Cursor Upgrade Migration loads about 2.1k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 60 tokens; SKILL.md has 589 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 589 words, ~2,137 tokens.

Download SKILL.mdSave it as .claude/skills/cursor-upgrade-migration/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
cursor-upgrade-migration
description
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".
allowed-tools
Read, Write, Edit, Bash(cmd:*)
compatibility
Designed for Claude Code
version
1.19.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, cursor, migration

Cursor Upgrade & Migration

Overview

Upgrade Cursor or migrate settings through a staged, reversible rollout that preserves policy, extensions, rules, workspace trust, and user recovery.

Prerequisites

  • Current/target versions, release-note review, supported-platform confirmation, and a settings backup.
  • Pilot users, a named migration owner, and an approved rollback or previous installer.

Instructions

  1. Inventory settings, extensions, rules, integrations, and identity/privacy requirements.
  2. Test the target version with a pilot using non-sensitive workspaces and required workflows.
  3. Document compatibility, performance, and policy results before broader rollout.
  4. Roll back or pause on sign-in, privacy, extension, or workflow regression; retain evidence for follow-up.

Output

  • A staged upgrade/migration record with pilot evidence, owner, compatibility decision, and rollback instructions.

Error Handling

ConditionSafe response
Upgrade breaks policy or privacy behaviorStop rollout, revert/pause, and escalate to the tenant owner.
Extension/settings migration failsRestore the verified backup and remediate in the pilot.
Version is unsupportedDo not force installation; use the supported version or plan platform remediation.

Examples

Back up a pilot user's settings, install the target version in a test profile, verify SSO, privacy, rules, indexing, and a sample repository, then expand only after the pilot receipt passes. Keep the previous installer until the observation window closes.

Upgrade Cursor IDE versions, migrate from VS Code, and transfer configurations between machines.

Version Upgrades

Cursor checks for updates automatically. When available:

  1. A notification appears: "A new version is available"
  2. Click "Restart to Update" or go to Help > Check for Updates
  3. Cursor downloads, installs, and restarts
Manual Update

If auto-update fails or is disabled:

bash
# macOS (Homebrew)
brew upgrade --cask cursor

# macOS/Linux/Windows: Download latest from
# https://cursor.com/download

# Linux AppImage: replace the old file
curl -fSL https://download.cursor.com/linux/appImage/x64 -o cursor.AppImage
chmod +x cursor.AppImage
Pre-Upgrade Checklist
[ ] Note current version: Help > About
[ ] Check release notes: changelog.cursor.sh
[ ] Backup settings:
    macOS: cp -r ~/Library/Application\ Support/Cursor/User ~/cursor-settings-backup
    Linux: cp -r ~/.config/Cursor/User ~/cursor-settings-backup
[ ] Export extension list:
    cursor --list-extensions > extensions-backup.txt
[ ] Commit any unsaved work to git
[ ] Note any custom keybindings (keybindings.json)
Post-Upgrade Verification
[ ] Cursor launches without errors
[ ] Sign-in still active (check top-right user icon)
[ ] AI features work: try Cmd+L, type a question
[ ] Tab completion works: type code, see ghost text
[ ] Extensions loaded: Cmd+Shift+X, verify list
[ ] Custom keybindings preserved: test your shortcuts
[ ] Project rules still load: @Cursor Rules in chat
[ ] Indexing status: check status bar

VS Code to Cursor Migration

Automatic Import (First Launch)

On first launch, Cursor detects VS Code and offers one-click import:

What migrates:
  ✅ settings.json (editor preferences)
  ✅ keybindings.json (custom shortcuts)
  ✅ User snippets
  ✅ Color themes
  ✅ Compatible extensions (from Open VSX Registry)

What does NOT migrate:
  ❌ Microsoft-exclusive extensions (Copilot, Live Share, Remote-SSH)
  ❌ Extension login states / databases
  ❌ Workspace trust settings
  ❌ Task configurations (.vscode/tasks.json -- copies but may need adjustment)
Manual Migration

If you skipped the auto-import:

bash
# Copy settings (macOS example)
cp ~/Library/Application\ Support/Code/User/settings.json \
   ~/Library/Application\ Support/Cursor/User/settings.json

# Copy keybindings
cp ~/Library/Application\ Support/Code/User/keybindings.json \
   ~/Library/Application\ Support/Cursor/User/keybindings.json

# Copy snippets
cp -r ~/Library/Application\ Support/Code/User/snippets/ \
      ~/Library/Application\ Support/Cursor/User/snippets/

# Reinstall extensions (from backup list)
while read ext; do cursor --install-extension "$ext"; done < extensions-backup.txt
Extension Marketplace Differences

Cursor uses Open VSX Registry instead of Microsoft's VS Code Marketplace:

ExtensionStatus in Cursor
ESLintAvailable (Open VSX)
PrettierAvailable (Open VSX)
GitLensAvailable (Open VSX)
DockerAvailable (Open VSX)
PythonAvailable (Open VSX)
GitHub CopilotNot available (Microsoft exclusive, also conflicts with Cursor AI)
Live ShareNot available (Microsoft exclusive)
Remote - SSHNot available (Microsoft exclusive)
C# Dev KitNot available (Microsoft exclusive)

For unavailable extensions, download .vsix from the VS Code Marketplace website and install manually: Cmd+Shift+P > Extensions: Install from VSIX...

Show full SKILL.md (212 more words)Show less
Running VS Code and Cursor Side-by-Side

Both can be installed simultaneously. They use separate:

  • Settings directories
  • Extension directories
  • Configuration files

You can open the same project in both editors at once (though be careful with file save conflicts).

Migration Between Machines

Export Configuration
bash
# List all extensions
cursor --list-extensions > cursor-extensions.txt

# Copy settings files
cp ~/Library/Application\ Support/Cursor/User/settings.json .
cp ~/Library/Application\ Support/Cursor/User/keybindings.json .

# Copy project rules (these are already in git if committed)
# .cursor/rules/*.mdc are project-level, not machine-level
Import on New Machine
bash
# Install Cursor
# Sign in (settings sync if available)

# Restore settings
cp settings.json ~/Library/Application\ Support/Cursor/User/
cp keybindings.json ~/Library/Application\ Support/Cursor/User/

# Install extensions
while read ext; do cursor --install-extension "$ext"; done < cursor-extensions.txt
Settings to Review After Machine Transfer
json
// settings.json -- platform-specific settings to check
{
  "terminal.integrated.defaultProfile.osx": "zsh",    // macOS
  "terminal.integrated.defaultProfile.linux": "bash",  // Linux
  "editor.fontFamily": "Fira Code",                    // Font must be installed
  "files.watcherExclude": { ... }                      // Paths may differ
}

Handling Breaking Changes

.cursorrules to .cursor/rules/ Migration

If upgrading from a Cursor version that used .cursorrules:

  1. Create .cursor/rules/ directory
  2. Split .cursorrules content into scoped .mdc files:
    • Global rules → project.mdc with alwaysApply: true
    • Language rules → typescript.mdc with globs: "**/*.ts"
  3. Test: open Chat, type @Cursor Rules to verify rules load
  4. Delete .cursorrules after confirming
Cursor 2.0 Changes

Cursor 2.0 introduced:

  • Agent-first architecture (Composer defaults to Agent mode)
  • New Composer model (faster generation)
  • Parallel agents (up to 8 simultaneous)
  • Bug fixes in Chat may appear as: settings key renames, deprecated fields

Check changelog.cursor.sh for specific breaking changes.

Enterprise Considerations

  • Managed deployment: Use MDM (macOS) or SCCM (Windows) to distribute Cursor with pre-configured settings
  • Version pinning: Enterprise admins can control which Cursor versions are deployed
  • Settings templates: Create a starter settings.json for new team members
  • Rollback: Keep the previous installer if an update causes issues; downgrade by reinstalling

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in skills/.curated/cursor-upgrade-migration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/errors.md
  • references/examples.md
  • references/migration-between-machines.md
  • references/pre-upgrade-checklist.md
  • references/troubleshooting-upgrades.md
  • references/upgrade-methods.md
  • references/vs-code-to-cursor-migration.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Cursor Upgrade Migration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cursor Upgrade Migration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cursor Upgrade Migration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.1kAutomated safety check: PassMIT
Release Roslynatordotnet/roslynator3.5k—~1kAutomated safety check: PassCustom licence
Trust CI Release GatesjohannesPettersson80/trust-platform222—~3.6kAutomated safety check: PassApache-2.0
Releasesignageos/vscode-sops122—~2.2kAutomated safety check: NotesMIT
Releasequerylenshq/ef-querylens225—~887Automated safety check: PassMIT
Changelog Entrycertinia/debug-log-analyzer114—~1.9kAutomated safety check: PassCustom licence

Similar skills

  • Release Roslynator

    dotnet/roslynator

    Official

    A skill your agent uses when shipping a roslynator release, rolling CHANGELOG.md [Unreleased], updating the VS Code extension changelog, creating a GitHub v release, or optionally tagging cli-v.

    3.5k GitHub stars~1k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • Trust CI Release Gates

    johannesPettersson80/trust-platform

    Prepares and ships truST changes - changelog and version updates, CI parity, pre-push checks, the exact-SHA release-candidate guard, merge, tag and release verification.

    222 GitHub stars~3.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Release

    signageos/vscode-sops

    Releases the vscode-sops extension end-to-end: determines the next version from the bump history, updates CHANGELOG.md and package.json/package-lock.json, builds via vscode:prepublish, publishes to…

    122 GitHub stars~2.2k tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes
  • Release

    querylenshq/ef-querylens

    A skill your agent uses when: creating a release, publishing a version, cutting a release, tagging a release, releasing plugin, release workflow, prepare release, create git tag, create GitHub…

    225 GitHub stars~887 tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Changelog Entry

    certinia/debug-log-analyzer

    Write, review or trim CHANGELOG.md entries. An agent skill from certinia/debug-log-analyzer.

    114 GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Changelog

    forcedotcom/salesforcedx-vscode

    Polish the automated CHANGELOG on develop before the next stable build.

    1k GitHub stars~3.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Cursor Upgrade Migration

What does Cursor Upgrade Migration do?

Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines. Cursor Upgrade Migration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Upgrade Cursor versions, migrate from VS Code, and transfer settings between machines.

When should I use Cursor Upgrade Migration?

Cursor Upgrade Migration fits situations like: Cursor migration; Cursor new version; vs code to cursor; Cursor changelog.

How do I install Cursor Upgrade Migration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-upgrade-migration -a claude-code`. Or copy the skill folder (skills/.curated/cursor-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/cursor-upgrade-migration in your project. Claude Code loads it when a task matches its description.

How do I install Cursor Upgrade Migration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-upgrade-migration -a codex`. Or copy the skill folder (skills/.curated/cursor-upgrade-migration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/cursor-upgrade-migration in your project. Codex loads it when a task matches its description.

Can I use Cursor Upgrade Migration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cursor-upgrade-migration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cursor-upgrade-migration, .gemini/skills/cursor-upgrade-migration, .github/skills/cursor-upgrade-migration and .opencode/skills/cursor-upgrade-migration in your project.

What does Cursor Upgrade Migration need to run?

Going by SKILL.md and its folder, Cursor Upgrade Migration needs the command-line tools its instructions call (cursor, brew and curl). Our summary lists: Python 3; Docker. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(cmd:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Cursor Upgrade Migration access the network?

SKILL.md names 4 domains. In commands or code: cursor.com and download.cursor.com; the agent is likely to contact these when it follows the instructions. As links in the text: changelog.cursor.sh and docs.cursor.com. This is read from the text; nothing was executed.

Is Cursor Upgrade Migration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cursor Upgrade Migration use?

Cursor Upgrade Migration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cursor Upgrade Migration use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.

What are the alternatives to Cursor Upgrade Migration?

Skills that share tags, products or a category with Cursor Upgrade Migration: Release Roslynator (dotnet/roslynator, 3.5k stars), Trust CI Release Gates (johannesPettersson80/trust-platform, 222 stars), Release (signageos/vscode-sops, 122 stars) and Release (querylenshq/ef-querylens, 225 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cursor Upgrade Migration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.