More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Expo Upgrade: SDK Upgrades Without the Lost Day

    1

    A runbook for Expo SDK upgrades: pre-flight checks, the upgrade sequence, managed vs bare native handling, deprecated-package migration, and post-upgrade housekeeping.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Expo Upgrade: SDK Upgrades Without the Lost Day

    Expo Upgrade: SDK Upgrades Without the Lost Day

    Example session with this skill installed

    Plan our upgrade from Expo SDK 55 to 57. We still use expo-av for audio and video, we are on the bare workflow, and we have two patches in patches/.

    • Read your context and instructions
    • Compiled the expo upgrade

    SDK 55 → 57 — upgrade plan produced with the skill

    Pre-flight: changelog shows expo-av removal pressure and a Hermes regression in early 57.x — target the latest 57 patch, not 56, skipping a known-bad intermediate. Inventory: expo-av in use for playback, two patches, no stale install excludes, bare workflow with committed native changes.

    Sequence (on a branch): expo install expo@57.x --fix, then doctor — clean before proceeding. Caches cleared aggressively (export --clear, remove node_modules and .expo, watchman reset) before any diagnosis. Bare workflow: prebuild --clean (safe — native changes committed), pod reinstall, gradle clean.

    Migration: expo-av → expo-audio and expo-video call-site by call-site, verifying each one, then uninstall; doctor re-run after the removal to catch required peers. Patches reviewed: one obsolete (the bug it fixed is gone in 57), deleted during the upgrade instead of "later."

    Housekeeping: sdkVersion removed, docs links bumped to the 57 path, react-native-worklets confirmed. Verification: audio playback, video, and every tab exercised on iOS and Android before merging. Rubric score: 9/10 — one point held back because the intermediate-step question (jump straight to 57 vs step through 56) was decided by the known-bad check, but the reasoning is recorded in the pre-flight note rather than in the branch description.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    An SDK upgrade is its own task — never bump versions by hand inside a feature branch. This skill treats it as a small project with three phases: pre-flight, the upgrade, and housekeeping. Pre-flight reads the target changelog, checks for known-bad releases, and inventories the risk surface (deprecated packages, config plugins, patches, stale install excludes) before anything is touched — on a branch you can abandon. The upgrade sequence runs install, fix, and doctor in order, with aggressive cache clearing before any diagnosis, because the most common upgrade "regression" is a stale cache. Native handling splits cleanly by workflow: managed projects skip the native steps entirely, bare projects regenerate with --clean only after hand-written native changes are committed.

    Deprecated packages migrate call-site by call-site before removal, with doctor re-run after each one to catch required peers that only break at native link time. Housekeeping deletes dead config, stale patches, and outlived workarounds. A worked example walks SDK 55 to 57 — skipping a known-bad intermediate, migrating expo-av, deleting an obsolete patch — with a scoring rubric gating the merge at 8/10.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    • It organizes the upgrade; it does not replace reading the target SDK's changelog — the changelog is the spec.
    • Verification needs real devices or simulators; the skill names what to test, it cannot run the test for you.
    • It does not upgrade dependencies unrelated to the SDK, and it does not fix app bugs the upgrade exposes — it surfaces them.
    • Large multi-version jumps may still need an intermediate step; the skill says how to decide, not how to avoid the work.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Software
    expoNode.jsexpo-doctor

    Permissions

    Terminal / Shell
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    No. The install commands exist to resolve the dependency graph; hand edits create a graph nobody verified. Use `expo install` and `--fix`, and let the tooling do the resolving.

    No — skip them entirely. There is nothing to regenerate, and running prebuild "just in case" creates native directories the project did not have, converting a managed project into a bare one by accident.

    No. Installation is not verification. The upgrade is done when the app runs: boot on iOS and Android, exercise camera/audio/video if the app uses them, navigate every stack, and run the test suite — with the results written down.

    New in Mobile Development