Agent skill · data analytics · sickn33
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.
Why this skill is useful
Provides specific commands and metrics for assessing EAS Update performance that the AI wouldn't reliably generate on its own.
What it needs
Requires eas-cli installed locally. Requires expo account access. About 6k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
EAS Update Insights Query the health of published EAS Updates directly from the CLI: launches, failed launches, crash rates, unique users, payload size, the embedded-vs-OTA user split per channel, and the most popular updates per runtime version. The data is the same data that powers the update and channel detail pages on expo.dev; these commands expose it in the terminal in human and JSON form. When to use this skill Use this when the user wants to assess the health or adoption of a published EAS Update: crash rates, install counts, unique users, bundle size, or the split between embedded and OTA users on a channel. Example prompts: "How is the latest update doing?" "Is the latest update healthy?" "Is the new release crashing more than the last one?" "How many users are on the latest update vs the embedded build?" "Which update is most popular on production right now?" "How big is our update bundle?" Also fits: post-publish rollout monitoring and regression detection. Don't use when the user needs per-user crash detail or device-level reporting; this skill only exposes aggregate EAS metrics. Prerequisites eas-cli installed (npm install -g eas-cli). Logged in: eas login. For channel:insights: run from an Expo project directory (the command resolves the project ID from app.json). update:insights only needs a login. Commands at a glance Command Purpose --- --- eas update:list Discover recent update groups, their group IDs, and branch names eas update:insights <groupId> Per-platform launches, failed launches, crash rate, unique users, payload size, daily breakdown eas update:view <groupId> --insights Update group details + the same metrics appended eas channel:insights --channel <name> --runtime-version <version> Embedded/OTA user counts, most popular updates, cumulative metrics for a channel + runtime All of these support --json --non-interactive for programmatic parsing. Discovering IDs Before querying insights for an update group, you need its group ID. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/eas-update-insights