π³ EAS Update Insights
Check the health of published EAS Updates β crash rates, launches, unique users, payload size and embedded vs OTA split
- What
- Check the health of published EAS Updates β crash rates, launches, unique users, payload size and embedded vs OTA split
- Cost
- Free
- Needs
- eas-cli installed and logged in (eas login); EAS is a paid Expo service β the data behind these commands counts against your plan's EAS Update usage
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ EAS is a paid Expo Application Services product β the data behind these commands counts against your plan's EAS Update usage. Curated by Skill Harbor β an official Expo skill that queries the health of published EAS Updates straight from the CLI: per-platform launches, failed launches, crash rates, unique users, payload size and daily breakdowns (`eas update:insights`), plus the embedded-vs-OTA user split per channel and the most popular updates per runtime version (`eas channel:insights`), in human or JSON form for CI gating and post-publish rollout monitoring. By @expo, listed here with credit to its creator. Honest caveats: aggregate metrics only β no per-user crash detail or device-level reporting; metrics lag the real-world state (crashes are self-reported on the next update check) and can double-count users running the same publish on both platforms. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: eas-cli installed and logged in (eas login); EAS is a paid Expo service β the data behind these commands counts against your plan's EAS Update usage Install "EAS Update Insights" for me. Check the health of published EAS Updates β crash rates, launches, unique users, payload size and embedded vs OTA split Repository: https://github.com/expo/skills/blob/main/plugins/expo/skills/eas-update-insights/SKILL.md 1. Fetch the SKILL.md file for the expo-eas-update-insights skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "expo-eas-update-insights". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat β credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.