Who it is forA mobile developer stuck on an old Expo SDK because upgrades break dependencies.
The problemSDK upgrades mean dependency conflicts, deprecated packages and cache problems that eat a day.
The outcomeAn app moved to the latest Expo SDK with conflicts and deprecated packages handled.
What you need first
- An Expo or React Native project
- Claude Code, Codex, Cursor or another agent that loads skills
- npx for the skills CLI
- An EAS account for the services skills (paid steps are labeled)
Steps
- Run
npx skills@latest add expo/skills --skill '*'from the project root, orclaude plugin install expo@claude-plugins-officialfor Claude Code - Restart or refresh your agent session so it finds the SKILL.md files
- Ask: Help me upgrade this app to the latest Expo SDK
- Let expo-upgrade work through dependency conflicts, deprecated packages and cache cleanup
- Run the app on a device or simulator and test before you commit
Prompt for your agent
Using the expo/skills expo-upgrade skill, upgrade this app to the latest Expo SDK. List each dependency conflict and deprecated package you change, and stop before committing so I can test.
Caveat. This card is written from the expo/skills README, not from a test run by Deduped. Before you start, make sure you have an Expo or React Native project. Check the repo for newer instructions before you rely on these steps.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for expo/skills and "Upgrade your app to the latest Expo SDK with an agent"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer