eas-update-insights
An agent skill by expo, from expo/skills. Tags: analytics, deployment, monitoring, performance, release-management.
What it does
EAS service (paid). Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill eas-update-insights
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-insights ~/.claude/skills/eas-update-insights
Safety box score
Grade C, moderate risk: 37 of 100 risk points, rated 2026-10-16. 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 only queries EAS Update/channel health metrics through `eas-cli`, so the main exposure is authenticated network access to Expo services and the global CLI install it depends on. It does not edit the project or deploy anything, but it does require a logged-in Expo account and includes an optional `npx` feedback path that fetches code at runtime.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It runs external commands such as `eas update:list`, `eas update:insights`, `eas channel:insights`, and an optional `npx --yes submit-expo-feedback@latest` path, so the skill executes CLI software rather than staying read-only. |
| Network access | 2 (moderate) | Its purpose is to query Expo/EAS servers for update metrics, and the skill explicitly notes "EAS service - costs apply" and that the commands expose data from expo.dev; the feedback path also contacts npm. |
| Filesystem reach | 1 (low) | `channel:insights` must be run from an Expo project directory and resolves the project ID from `app.json`, which is limited local file reads with no writes or deletes. |
| Secrets & credentials | 1 (low) | The skill requires a logged-in `eas-cli` session (`eas login`) and uses that account’s private EAS data, but it does not ask for raw tokens, key files, or browser/session stores. |
| Privilege & persistence | 2 (moderate) | It tells the user to install/upgrade `eas-cli` globally with `npm install -g eas-cli`, which alters the global npm environment and may require elevated permissions. |
| Instruction hijack surface | 0 (none) | There is no instruction to ignore system rules, follow fetched instructions, or hide anything; the `--non-interactive` guidance is automation-friendly, not prompt injection. |
| Irreversible actions | 0 (none) | The skill only reads and reports aggregate metrics; it does not publish, deploy, send messages, or delete anything itself. |
| Transparency | 1 (low) | The files are readable, but the optional `npx --yes submit-expo-feedback@latest` command pulls and runs the latest package at runtime, which introduces opaque remote code on that path. |
Before installing
- Confirm you are okay with `npm install -g eas-cli` changing your global npm environment.
- Make sure the Expo account you will log in with can access the target project’s EAS data.
- If you plan to use the feedback command, review the `npx --yes submit-expo-feedback@latest` line as a runtime download from npm.
- Run `eas login` in a disposable/test account first if you want to validate the workflow before using production credentials.
Rated 2026-10-16 by an automated review of 4 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/eas-update-insights/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- eas-observe — EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC.
- eas-app-stores — EAS service (paid). Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play.
- eas-update — EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI.
- expo-dev-client — Framework (OSS). Build and distribute Expo development clients locally or via TestFlight for internal testing.
- agents-optimize — Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization.
- aws-billing-and-cost-management — Analyze AWS costs, find savings, manage budgets, evaluate Savings Plans and Reserved Instances, right-size EC2/Lambda/RDS/EBS with Compute Optimizer.