Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/upgrading-expo
Guidelines for upgrading Expo SDK versions and fixing dependency issues
Passed 23 of 23 test cases with the skill, and 14 of 23 without it.
and 14 more in the full report
9 fixed14 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to test an unreleased preview version of the upcoming Expo SDK. How do preview releases tag their versions and what is the CLI command to install the preview release?
| Checked | Without skill | With skill |
|---|---|---|
| specifies running npx expo install expo@next --fix to install beta releases | Missed | Passed |
| notes that preview versions use the -preview suffix published under the @next tag | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when you need guidelines for upgrading Expo SDK versions and fixing dependency issues.
@react-navigation/* imports to expo-router entry points (codemod + manual mapping)Beta versions use .preview suffix (e.g., 55.0.0-preview.2), published under @next tag.
Check if latest is beta: https://exp.host/--/api/v2/versions (look for -preview in expoVersion)
npx expo install expo@next --fix # install beta
npx expo install expo@latest
npx expo install --fix
Run diagnostics: npx expo-doctor
Clear caches and reinstall
npx expo export -p ios --clear
rm -rf node_modules .expo
test cases passed, vs 14 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.