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...
Profile →npx skills add sickn33/agentic-awesome-skills --skill eas-update-insights --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`). - Logg
- When to use this skill
- Prerequisites
- Commands at a glance
- Discovering IDs
- eas update:insights <groupId>
- Basic use
- Flags
- JSON output shape
- Errors
- eas update:view <groupId> --insights
- eas channel:insights --channel <name> --runtime-version <version>
- Common workflows
- Verify the update I just published is healthy
- Compare adoption between two channels
Latest group id across all branches eas update:list --all --json --non-interactive | jq -r '.currentPage[0].group' Latest group id on a specific branch eas update:list --branch production --json --non-interactive | jq -r '.currentPage[0].group' eas update:insights 03d5dfcf-736c-475a-8730-af039c3f4d06 Human-readable eas update:view 03d5dfcf-... --insights eas update:view 03d5dfcf-... --insights --days 30 eas update:view 03d5dfcf-... --json --insights eas channel:insights --channel production --runtime-version 1.0.6
What does the eas-update-insights skill do?
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...
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill eas-update-insights --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.