expo-upgrade
An agent skill by expo, from expo/skills. Tags: dependencies, development, migration, setup, troubleshooting.
What it does
Framework (OSS). Guidelines for upgrading Expo SDK versions and fixing dependency issues
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-upgrade
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/expo-upgrade ~/.claude/skills/expo-upgrade
Safety box score
Grade C, moderate risk: 26 of 100 risk points, rated 2026-10-20. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is a documentation-heavy Expo upgrade playbook, but it includes commands that can install packages, rewrite imports, regenerate native projects, and clear local build state. The main risks are destructive local cleanup (`rm -rf node_modules .expo`) and outbound network activity through `npx`/feedback commands.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It explicitly runs external tools and scripts such as `npx expo install expo@latest`, `npx expo-codemod ...`, `npx expo prebuild --clean`, and `cd android && ./gradlew clean`. |
| Network access | 2 (moderate) | It fetches and runs registry packages via `npx` and points to remote Expo services like `https://exp.host/--/api/v2/versions` and `npx --yes submit-expo-feedback@latest ...`. |
| Filesystem reach | 1 (low) | Its actions stay in the project tree but include destructive cleanup and regeneration, notably `rm -rf node_modules .expo` and `npx expo prebuild --clean`. |
| Secrets & credentials | 0 (none) | It does not ask for or access tokens, `.env` files, keychains, browser sessions, or other secret stores. |
| Privilege & persistence | 0 (none) | There is no `sudo`, global install, service registration, or OS/shell configuration change. |
| Instruction hijack surface | 1 (low) | It tells the agent to `load the expo-skill-feedback skill and follow its eval-candidate flow`, which introduces another instruction source, but it does not instruct bypassing safeguards or hiding actions. |
| Irreversible actions | 1 (low) | It can automatically perform upgrades, codemods, package removals, and cache clears, but it does not deploy, publish, message, pay, or book anything external. |
| Transparency | 0 (none) | All shipped files are readable markdown/YAML; there are no binaries, embedded blobs, or opaque installers. |
Before installing
- Confirm you are okay with deleting `node_modules` and `.expo` in the repo.
- Review the `npx ...@latest` commands and decide whether you want registry-fetched tools to run.
- Check whether you want the optional Expo feedback command available, since it sends data to Expo.
Rated 2026-10-20 by an automated review of 9 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-upgrade/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- unity-package-management — Use when adding, removing, upgrading, or discovering Unity (UPM) packages programmatically from outside the Editor — headless or CI package installs via the C#.
- expo-dom — Framework (OSS). Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
- expo-project-structure — Framework (OSS). Folder structure for a new Expo app.
- expo-web-to-native — Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo.
- expo-migrate-module — Framework (OSS). Migrate an existing Apple/Swift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2).
- app-platform-migration — Migrate applications from Heroku, AWS, Render, Railway, Fly.io, or Docker Compose to DigitalOcean App Platform. Use when converting existing apps.