PlugWiki

eas-update (Expo): a Claude skill that sets up and publishes EAS over-the-air updates

The eas-update skill makes Claude set up EAS Update, publish over-the-air JavaScript updates to a channel, and work out why an app still shows old code.

Installs
12.3K
on skills.sh
Stars
4K
on GitHub
Files
1
besides SKILL.md
Updated
Nov 2026
last repo commit

Ask Claude to set up OTA updates, publish to preview or production, or explain why a TestFlight build did not update, and this Expo skill sets the process. Claude checks your package.json, app config and eas.json first. It then runs npx expo install expo-updates and eas update:configure rather than writing config by hand, and shows you the resulting diff.

It explains builds, updates, branches, channels and runtime versions, and when you need a new native build instead of an update. Publishing changes live state, so SKILL.md tells Claude to confirm the project, channel, environment and message first, and to publish to production only after you approve. EAS Update uses plan allowances, and the skill links to Expo pricing.

Good for

  • Expo and React Native developers shipping JavaScript fixes without a new store build
  • Teams setting up preview, staging and production update channels
  • Developers debugging a build that still shows old code

Install eas-update

Claude Code

  1. 1

    Copy this prompt.

    Install the eas-update skill in Claude Code. Run this command:
    
    claude plugin install expo@claude-plugins-official
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

The expo plugin installs 23 skills and a bundled Expo MCP server at https://mcp.expo.dev/mcp, not just eas-update. The skills CLI command installs only this skill. The skill runs EAS CLI on your machine, so the Claude app ZIP upload is not offered here. You can also run /plugin install expo@claude-plugins-official inside Claude Code.

From the project README. Source.

What's in the skill

When it loads

Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI. Use when setting up OTA updates, running eas update:configure or eas update, publishing to preview/staging/production channels, explaining branches/channels/runtime versions, testing updates, or debugging why an installed build still shows old code. Load for TestFlight, preview, or production updates that do not appear, including questions about cold launches or reopening the app. Not for update health metrics; use eas-update-insights for adoption, crashes, and rollout monitoring.

Sections in SKILL.md

  1. Start with the supported configuration path
  2. Keep the model straight
  3. Decide whether an update is compatible
  4. Publish deliberately
  5. Test according to the build type
  6. Development builds
  7. Preview, TestFlight, and production builds
  8. Debug a build that did not update
  9. Advanced and adjacent workflows
  10. Official references
  11. Submitting Feedback

Key facts

License
MIT
Installs on skills.sh
12,262 as of 2026-11-02
Last repo commit
2026-11-01

What it includes

  • Reads package.json, app config and eas.json before changing anything.

    Files · Inspect first

  • Installs the SDK-compatible expo-updates package.

    Runs code · expo install expo-updates

  • Links the project and writes update config through the CLI.

    Runs code · eas update:configure

  • Explains how an installed build finds its update.

    Build, update, branch, channel

  • Decides if a change fits an update or needs a new native build.

    Compatibility check

  • Publishes an update to a channel with a message and environment.

    Runs code · eas update

  • Development builds versus preview, TestFlight and production launch rules.

    Testing by build type

  • A six-step check from project and channel to cold launches.

    Runs code · Debugging an update that did not apply

  • Points to Expo docs for overriding a build's channel header.

    Channel surfing

  • Sends feedback to Expo with @expo/agent-cli when there is something specific.

    Runs code · Feedback command

From the official docs

Permissions

Medium risk

Claude runs Expo and EAS commands that can change your project files and publish updates to real users' apps. Approve each publish yourself and use a preview channel first.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Publishing changes what your users run

    `eas update` publishes JavaScript and assets to a channel. SKILL.md says to confirm project, channel, environment and message first, and to publish to production only after approval. Use a preview channel to test.

  • It runs the latest EAS CLI with npx

    The commands use `npx eas-cli@latest`, which downloads and runs the newest release each time. Allowed tools are npx expo, npx eas-cli and eas commands.

  • The plugin route adds an MCP server

    The expo plugin bundles an MCP config for https://mcp.expo.dev/mcp, which the README says can trigger and monitor EAS builds. The skills CLI route for this one skill does not add it.

  • The skill can send feedback to Expo

    It includes a `npx --yes @expo/agent-cli@latest feedback` command for specific problems with the skill. Check what it will send before you let Claude run it.

Technical details
Talks tomcp.expo.dev (expo plugin route only)
Sign-in and keysNot stated in SKILL.md. EAS CLI commands run against the Expo project you have linked.

Questions

What does the eas-update skill do?

It guides Claude through EAS Update with expo-updates and EAS CLI. That covers setup, publishing to channels, how branches, channels and runtime versions fit together, testing by build type, and debugging updates that do not show up.

How do I install it?

Use the install box above. For Claude Code and Codex, Expo's README recommends the expo plugin, which installs all of Expo's skills. The skills CLI command installs only this skill. For other agents the README uses the skills CLI.

What does the expo plugin bundle?

The expo plugin in the repo holds 23 skills and an MCP configuration for the Expo MCP server at mcp.expo.dev. The README says that server can read Expo docs, install dependencies, trigger and monitor EAS builds and workflows, and read crash data. The plugin.json lists no hooks.

Does it cost money?

EAS Update is on the Free plan, and publishing and delivery use update, bandwidth and storage allowances, with higher limits on paid plans. SKILL.md links to Expo's pricing page.

Will it publish to production on its own?

No. SKILL.md says to publish to production only when you have asked for it or approved it. If the target is unclear, Claude should stop and ask, and should not guess production from your Git branch.

Why does my TestFlight build still show old code?

SKILL.md says release builds usually start with the current update and download the new one in the background. Fully close the app and reopen it, then do it once more if needed. That can take up to two cold launches.

Is it safe?

It runs EAS CLI and Expo commands that can change remote state, and npx eas-cli@latest fetches the newest CLI each time. Check the channel, environment and runtime version before you approve a publish. The skill also tells Claude how to send feedback to Expo with @expo/agent-cli, which you can decline.

When do I need a new build instead?

When a change adds or edits native code or native configuration, including most native library additions and SDK upgrades. An update only carries JavaScript, styling and assets the installed build already supports.

Information

updated Nov 2, 2026

Repository
expo/skills
Folder
plugins/expo/skills/eas-update

expo/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5
  1. expo/skills README · github.com
  2. expo plugin.json · github.com
  3. expo .mcp.json · github.com
  4. eas-update SKILL.md · github.com
  5. eas-update on skills.sh · skills.sh

Updated Nov 2, 2026.