eas-update
An agent skill by expo, from expo/skills. Tags: assets, configuration, deployment, javascript, mobile, release-management.
What it does
EAS service (paid). 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.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill eas-update
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/eas-update ~/.claude/skills/eas-update
Safety box score
Grade C, moderate risk: 42 of 100 risk points, rated 2026-09-22. 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 configures and publishes Expo EAS Updates, using `npx` to run Expo/EAS CLI commands that can modify the project and talk to Expo’s hosted services. The main risk is remote OTA publishing: it can change what installed apps execute, including production if explicitly approved. It also auto-installs/configures packages and can submit feedback over the network.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It runs registry-backed CLI commands such as `npx expo install expo-updates`, `npx eas-cli@latest update:configure`, and `npx --yes submit-expo-feedback@latest`, so it can execute downloaded code in the project context. |
| Network access | 2 (moderate) | The workflow sends data to Expo/EAS services when configuring, publishing, or submitting feedback, and it depends on remote docs and CLI help URLs. |
| Filesystem reach | 2 (moderate) | It can rewrite project files and native config through `expo install` and `eas update:configure`, including tracked `ios/` or `android/` directories when present. |
| Secrets & credentials | 1 (low) | Publishing depends on an authenticated EAS account and an EAS environment for SDK 55+, but the skill does not directly instruct reading local secret stores or keychains. |
| Privilege & persistence | 0 (none) | There is no sudo, global install, service registration, shell-profile editing, or other OS privilege escalation in the skill. |
| Instruction hijack surface | 1 (low) | The feedback command uses `--yes`, which skips a confirmation prompt, but the skill does not tell the agent to ignore its own rules or hide content. |
| Irreversible actions | 3 (high) | Publishing OTA updates is the skill’s purpose and it explicitly says this can affect installed applications; it can publish to production when the user approves. |
| Transparency | 0 (none) | All shipped files are plain text; there are no binaries, base64 blobs, or hidden runtime-generated commands. |
Before installing
- Read `SKILL.md` for the exact `update:configure` and `update` commands it will run.
- Check `package.json`, `app.config.*`, and `eas.json` to see what files/config may change.
- Confirm which EAS account and environment variables will be used before any publish.
- If you might publish to production, verify the target channel/branch and runtime version first.
Rated 2026-09-22 by an automated review of 2 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/eas-update/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- eas-app-stores — EAS service (paid). Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play.
- expo-dev-client — Framework (OSS). Build and distribute Expo development clients locally or via TestFlight for internal testing.
- eas-hosting — EAS service (paid). Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs.
- eas-update-insights — EAS service (paid). Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size.
- expo-app-clip — Framework (OSS). Add an iOS App Clip target to an Expo app.
- deployment — Deploy applications to DigitalOcean App Platform via GitHub Actions with proper environment management and secrets handling.