Back to Skills

eas-update-insights

Check the health of published EAS Updates: 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.

1,896stars87forksUpdated 5/12/2026

Security Assessment

Safe(100/100)
Security Score100/100

About eas-update-insights

The `eas-update-insights` skill provides developers with a streamlined way to monitor the health and adoption of published EAS (Expo Application Services) Updates. By querying aggregate metrics directly from the CLI, this skill helps teams understand how their updates are performing in production without needing per-device analytics. It addresses common questions about update stability, user adoption, and the distribution of updates across embedded and over-the-air (OTA) builds, enabling developers to make informed decisions about rollouts and continuous integration gating based on update health.

Key features include the ability to retrieve launch counts, failed launches, crash rates, unique user counts, payload sizes, and the distribution between embedded and OTA users per channel. Users can also identify the most popular updates per runtime version and access both human-readable and JSON output for programmatic processing. Commands like `eas update:list`, `eas update:insights`, `eas update:view --insights`, and `eas channel:insights` provide flexible options to discover recent update groups, inspect metrics for specific updates, and analyze channel-wide statistics. All commands support non-interactive and JSON output modes for automation in scripts or CI pipelines.

This skill is particularly useful for mobile developers, release managers, and CI/CD engineers who need to monitor update rollouts, detect regressions, and ensure overall stability of their apps. It is designed for scenarios such as checking the latest update's health, comparing embedded vs OTA adoption, tracking bundle sizes, and identifying which update is currently most popular. It is not intended for per-user crash details or device-level reporting, making it suitable for aggregate-level insights and operational decision-making rather than detailed debugging.

FAQ

What does `eas-update-insights` do?

It queries aggregate metrics for published EAS Updates, including launch counts, crash rates, payload sizes, unique users, and the split between embedded and OTA users.

Which commands are available for querying update insights?

You can use `eas update:list` to discover update groups, `eas update:insights <groupId>` for detailed metrics, `eas update:view <groupId> --insights` for update details, and `eas channel:insights` for channel-wide insights.

What are the prerequisites for using this skill?

You need `eas-cli` installed, be logged in with `eas login`, and for channel-level insights, run the commands from an Expo project directory.

Can I get per-user crash or device-level data?

No, this skill only provides aggregate metrics and does not expose per-user or device-specific crash data.

Can I use this skill in automated scripts or CI pipelines?

Yes, all commands support `--json --non-interactive` flags for programmatic parsing and automation.

All Files

3 files
SKILL.md11.1 KB
View
references/channel-insights-schema.md2.3 KB
View
references/update-insights-schema.md2.5 KB
View

Install eas-update-insights

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

expo/skills