[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPPR2GMSJFZ6D026J335Y7":3,"skill-same:01M7EPPR2GMSJFZ6D026J335Y7":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":13,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EPPR2GMSJFZ6D026J335Y7","eas-update-insights",null,"Check the health of published EAS Update: crash rates, install\u002Flaunch 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.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Feas-update-insights\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: eas-update-insights\ndescription: \"Check the health of published EAS Update: crash rates, install\u002Flaunch 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.\"\nversion: 1.0.0\nlicense: MIT\nallowed-tools: \"Bash(eas *)\"\n---\n\n# EAS Update Insights\n\n> **EAS service - costs apply.** Insights cover updates published through EAS Update, a paid Expo Application Services product with free-tier limits. Update delivery and the data behind these commands count against your plan's EAS Update usage. Review https:\u002F\u002Fexpo.dev\u002Fpricing.\n\nQuery the health of published EAS Update 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.\n\n## When to use this skill\n\nUse 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.\n\nExample prompts:\n\n- \"How is the latest update doing?\"\n- \"Is the latest update healthy?\"\n- \"Is the new release crashing more than the last one?\"\n- \"How many users are on the latest update vs the embedded build?\"\n- \"Which update is most popular on production right now?\"\n- \"How big is our update bundle?\"\n\nAlso fits: post-publish rollout monitoring and regression detection.\n\nDon't use when the user needs per-user crash detail or device-level reporting; this skill only exposes aggregate EAS metrics.\n\n## Prerequisites\n\n- `eas-cli` installed (`npm install -g eas-cli`).\n- Logged in: `eas login`.\n- For `channel:insights`: run from an Expo project directory (the command resolves the project ID from `app.json`). `update:insights` only needs a login.\n\n## Commands at a glance\n\n| Command | Purpose |\n|---|---|\n| `eas update:list` | Discover recent update groups, their `group` IDs, and branch names |\n| `eas update:insights \u003CgroupId>` | Per-platform launches, failed launches, crash rate, unique users, payload size, daily breakdown |\n| `eas update:view \u003CgroupId> --insights` | Update group details + the same metrics appended |\n| `eas channel:insights --channel \u003Cname> --runtime-version \u003Cversion>` | Embedded\u002FOTA user counts, most popular updates, cumulative metrics for a channel + runtime |\n\nAll of these support `--json --non-interactive` for programmatic parsing.\n\n## Discovering IDs\n\nBefore querying insights for an update group, you need its `group` ID. Use `eas update:list` with either `--branch \u003Cname>` (updates on that branch) or `--all` (updates across all branches). Always pass `--json --non-interactive` when running non-interactively; without a branch\u002F`--all` flag the command will otherwise prompt for a branch selection:\n\n```bash\n# Latest group id across all branches\neas update:list --all --json --non-interactive | jq -r '.currentPage[0].group'\n\n# Latest group id on a specific branch\neas update:list --branch production --json --non-interactive | jq -r '.currentPage[0].group'\n```\n\nThe JSON response has a `currentPage` array with one entry per update group (both platforms of the same publish are collapsed into one entry):\n\n```json\n{\n  \"currentPage\": [\n    {\n      \"branch\": \"production\",\n      \"message\": \"\\\"Fix checkout crash\\\" (1 week ago by someone)\",\n      \"runtimeVersion\": \"1.0.6\",\n      \"group\": \"03d5dfcf-736c-475a-8730-af039c3f4d06\",\n      \"platforms\": \"android, ios\",\n      \"isRollBackToEmbedded\": false\n    }\n  ]\n}\n```\n\nEntries also carry `codeSigningKey` and `rolloutPercentage`, but only when those features are in use for the group (undefined values are omitted from the JSON output).\n\nWhen called with `--branch \u003Cname>`, the response also includes `name` (the branch name) and `id` (the branch ID) at the top level.\n\n## `eas update:insights \u003CgroupId>`\n\nShows launches, failed launches, crash rate, unique users, launch asset count, and average payload size for a single update group, broken down **per platform** (iOS, Android), plus a daily breakdown of launches and failures.\n\n### Basic use\n\n```bash\neas update:insights 03d5dfcf-736c-475a-8730-af039c3f4d06\n```\n\n### Flags\n\n| Flag | Description |\n|---|---|\n| `--days \u003CN>` | Look back N days. Default: **7**. Mutually exclusive with `--start`\u002F`--end`. |\n| `--start \u003Ciso-date>` \u002F `--end \u003Ciso-date>` | Explicit time range, e.g. `--start 2026-04-01 --end 2026-04-15`. |\n| `--platform \u003Cios\\|android>` | Filter to a single platform. Omit to see all platforms in the group. |\n| `--json` | Machine-readable output. Implies `--non-interactive`. |\n| `--non-interactive` | Required when scripting. |\n\n### JSON output shape\n\nTop level: `groupId`, `timespan` (`start`, `end`, `daysBack`), and `platforms[]` with one entry per platform the group was published to. Each platform entry has `updateId`, `totals` (`uniqueUsers`, `installs`, `failedInstalls`, `crashRatePercent`), `payload` (`launchAssetCount`, `averageUpdatePayloadBytes`), and a `daily[]` time series of `{ date, installs, failedInstalls }`.\n\nFor the complete schema and field reference, see [references\u002Fupdate-insights-schema.md](.\u002Freferences\u002Fupdate-insights-schema.md).\n\nFields that matter for health assessment:\n\n- `platforms[].totals.crashRatePercent`, computed as `failedInstalls \u002F (installs + failedInstalls) * 100`. Zero when there are no installs.\n- `platforms[].totals.installs` and `uniqueUsers` give the adoption signal.\n- `platforms[].daily` is a time series, useful for spotting a sudden spike in failures.\n\n### Errors\n\n- `Could not find any updates with group ID: \"\u003Cid>\"` — group doesn't exist or you lack access.\n- `Update group \"\u003Cid>\" has no ios update (available platforms: android)` — `--platform ios` was used but the group wasn't published for iOS.\n- `EAS Update insights is not supported by this version of eas-cli. Please upgrade ...` — the server deprecated a field the CLI relies on. Run `npm install -g eas-cli@latest`.\n\n## `eas update:view \u003CgroupId> --insights`\n\nExtends the standard `update:view` output with the same per-platform insights, inline.\n\n```bash\n# Human-readable\neas update:view 03d5dfcf-... --insights\neas update:view 03d5dfcf-... --insights --days 30\n\n# JSON: wrapped as { updates: [...], insights: {...} }\neas update:view 03d5dfcf-... --json --insights\n```\n\nWithout `--insights`, `update:view` behaves exactly as before — no JSON shape change for existing consumers. The `--days` \u002F `--start` \u002F `--end` flags only apply when `--insights` is set; passing them alone errors.\n\n## `eas channel:insights --channel \u003Cname> --runtime-version \u003Cversion>`\n\nShows, per channel, how many users are on the embedded build vs over-the-air updates and which updates are pulling the most traffic. Must be run from an Expo project directory.\n\n### Basic use\n\n```bash\neas channel:insights --channel production --runtime-version 1.0.6\n```\n\n### Flags\n\n| Flag | Description |\n|---|---|\n| `--channel \u003Cname>` | **Required.** The channel name (e.g. `production`, `staging`). |\n| `--runtime-version \u003Cversion>` | **Required.** Match exactly what was published. Check `runtimeVersion` values in `update:list`. |\n| `--days \u003CN>` | Look back N days. Default: **7**. |\n| `--start` \u002F `--end` | Explicit time range, like `update:insights`. |\n| `--json` \u002F `--non-interactive` | Machine-readable output. |\n\n### JSON output shape\n\nTop level: `channel`, `runtimeVersion`, `timespan`, `embeddedUpdateTotalUniqueUsers`, `otaTotalUniqueUsers`, `mostPopularUpdates[]` (each with `rank`, `groupId`, `message`, `platform`, `totalUniqueUsers`), `cumulativeMetricsAtLastTimestamp[]`, plus chart-shaped `uniqueUsersOverTime` and `cumulativeMetricsOverTime` objects with `labels` and `datasets`.\n\nFor the complete schema and field reference, see [references\u002Fchannel-insights-schema.md](.\u002Freferences\u002Fchannel-insights-schema.md).\n\nFields that matter:\n\n- `embeddedUpdateTotalUniqueUsers` is the count of users running the embedded (binary-bundled) build.\n- `mostPopularUpdates[]` is updates ranked by `totalUniqueUsers`. **Caveat**: this is the top-N the server returns; `otaTotalUniqueUsers` is a sum of that list and may undercount total OTA reach if more than top-N updates are active.\n- `uniqueUsersOverTime` and `cumulativeMetricsOverTime` are daily data series for charting.\n\n### Errors\n\n- `Could not find channel with the name \u003Cname>` — typo or wrong account.\n- \"No update launches recorded\" in the table \u002F empty `mostPopularUpdates` in JSON — no OTA update has been launched for that channel + runtime yet. Usually means the channel is still serving the embedded build only.\n\n## Common workflows\n\n### Verify the update I just published is healthy\n\n```bash\n# 1. Grab the latest publish on production\nGROUP_ID=$(eas update:list --branch production --json --non-interactive \\\n  | jq -r '.currentPage[0].group')\n\n# 2. Give it some adoption time (minutes to hours), then check crash rate\neas update:insights \"$GROUP_ID\" --json --non-interactive \\\n  | jq '.platforms[] | {platform, installs: .totals.installs, crashRate: .totals.crashRatePercent}'\n```\n\nCompare the `crashRate` across platforms and against previous releases; sudden spikes or asymmetric behaviour (iOS spiking while Android is flat, or vice versa) is the signal to investigate.\n\n### Compare adoption between two channels\n\n```bash\nfor channel in production staging; do\n  echo \"--- $channel ---\"\n  eas channel:insights --channel \"$channel\" --runtime-version 1.0.6 --json --non-interactive \\\n    | jq '{\n        channel,\n        embedded: .embeddedUpdateTotalUniqueUsers,\n        ota: .otaTotalUniqueUsers,\n        topUpdate: .mostPopularUpdates[0]\n      }'\ndone\n```\n\n### Detect a rollout regression in the last 24 hours\n\n```bash\neas update:insights \"$GROUP_ID\" --days 1 --json --non-interactive \\\n  | jq '.platforms[] | select(.totals.crashRatePercent > 1)'\n```\n\n### Summarize group metrics for release notes\n\n```bash\neas update:view \"$GROUP_ID\" --insights --days 30\n```\n\nHuman-readable group details plus 30 days of launches\u002Ffailures per platform — suitable for pasting into a changelog or incident review.\n\n## Output tips\n\n- Pipe JSON through `jq`; payloads are structured for easy filtering.\n- `--json` implies `--non-interactive`, but passing both is explicit and scripting-friendly.\n- Dates in `daily[].date` are UTC ISO timestamps; the human-readable table renders them as `YYYY-MM-DD` (UTC).\n- The CLI table labels say \"Launches\" \u002F \"Crashes\" while JSON uses `installs` \u002F `failedInstalls`. Same field, different display name.\n\n## Limitations\n\n- **Unique users across platforms** may double-count users who run the same publish on both iOS and Android. The same caveat applies to `otaTotalUniqueUsers` in channel insights, which is a sum over `mostPopularUpdates`.\n- **Fresh publishes** may show zeros for a short period while the metrics pipeline catches up.\n- **Installs are downloads, not launches**: the `installs` \u002F \"Launches\" field counts users who downloaded the manifest and launch asset. A confirmed run only registers on the user's *next* update check (typically up to 24h later, depending on the app's update policy). So metrics lag the real-world state slightly.\n- **Crashes are self-reported**: `failedInstalls` \u002F \"Crashes\" counts updates that errored during install\u002Flaunch and were reported on the next update check. Crashes that don't trigger an update request (e.g. process kill before recovery) won't appear.\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"eas-update-insights\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n","# EAS Update Insights\n\n> **EAS service - costs apply.** Insights cover updates published through EAS Update, a paid Expo Application Services product with free-tier limits. Update delivery and the data behind these commands count against your plan's EAS Update usage. Review https:\u002F\u002Fexpo.dev\u002Fpricing.\n\nQuery the health of published EAS Update 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.\n\n## When to use this skill\n\nUse 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.\n\nExample prompts:\n\n- \"How is the latest update doing?\"\n- \"Is the latest update healthy?\"\n- \"Is the new release crashing more than the last one?\"\n- \"How many users are on the latest update vs the embedded build?\"\n- \"Which update is most popular on production right now?\"\n- \"How big is our update bundle?\"\n\nAlso fits: post-publish rollout monitoring and regression detection.\n\nDon't use when the user needs per-user crash detail or device-level reporting; this skill only exposes aggregate EAS metrics.\n\n## Prerequisites\n\n- `eas-cli` installed (`npm install -g eas-cli`).\n- Logged in: `eas login`.\n- For `channel:insights`: run from an Expo project directory (the command resolves the project ID from `app.json`). `update:insights` only needs a login.\n\n## Commands at a glance\n\n| Command | Purpose |\n|---|---|\n| `eas update:list` | Discover recent update groups, their `group` IDs, and branch names |\n| `eas update:insights \u003CgroupId>` | Per-platform launches, failed launches, crash rate, unique users, payload size, daily breakdown |\n| `eas update:view \u003CgroupId> --insights` | Update group details + the same metrics appended |\n| `eas channel:insights --channel \u003Cname> --runtime-version \u003Cversion>` | Embedded\u002FOTA user counts, most popular updates, cumulative metrics for a channel + runtime |\n\nAll of these support `--json --non-interactive` for programmatic parsing.\n\n## Discovering IDs\n\nBefore querying insights for an update group, you need its `group` ID. Use `eas update:list` with either `--branch \u003Cname>` (updates on that branch) or `--all` (updates across all branches). Always pass `--json --non-interactive` when running non-interactively; without a branch\u002F`--all` flag the command will otherwise prompt for a branch selection:\n\n```bash\n# Latest group id across all branches\neas update:list --all --json --non-interactive | jq -r '.currentPage[0].group'\n\n# Latest group id on a specific branch\neas update:list --branch production --json --non-interactive | jq -r '.currentPage[0].group'\n```\n\nThe JSON response has a `currentPage` array with one entry per update group (both platforms of the same publish are collapsed into one entry):\n\n```json\n{\n  \"currentPage\": [\n    {\n      \"branch\": \"production\",\n      \"message\": \"\\\"Fix checkout crash\\\" (1 week ago by someone)\",\n      \"runtimeVersion\": \"1.0.6\",\n      \"group\": \"03d5dfcf-736c-475a-8730-af039c3f4d06\",\n      \"platforms\": \"android, ios\",\n      \"isRollBackToEmbedded\": false\n    }\n  ]\n}\n```\n\nEntries also carry `codeSigningKey` and `rolloutPercentage`, but only when those features are in use for the group (undefined values are omitted from the JSON output).\n\nWhen called with `--branch \u003Cname>`, the response also includes `name` (the branch name) and `id` (the branch ID) at the top level.\n\n## `eas update:insights \u003CgroupId>`\n\nShows launches, failed launches, crash rate, unique users, launch asset count, and average payload size for a single update group, broken down **per platform** (iOS, Android), plus a daily breakdown of launches and failures.\n\n### Basic use\n\n```bash\neas update:insights 03d5dfcf-736c-475a-8730-af039c3f4d06\n```\n\n### Flags\n\n| Flag | Description |\n|---|---|\n| `--days \u003CN>` | Look back N days. Default: **7**. Mutually exclusive with `--start`\u002F`--end`. |\n| `--start \u003Ciso-date>` \u002F `--end \u003Ciso-date>` | Explicit time range, e.g. `--start 2026-04-01 --end 2026-04-15`. |\n| `--platform \u003Cios\\|android>` | Filter to a single platform. Omit to see all platforms in the group. |\n| `--json` | Machine-readable output. Implies `--non-interactive`. |\n| `--non-interactive` | Required when scripting. |\n\n### JSON output shape\n\nTop level: `groupId`, `timespan` (`start`, `end`, `daysBack`), and `platforms[]` with one entry per platform the group was published to. Each platform entry has `updateId`, `totals` (`uniqueUsers`, `installs`, `failedInstalls`, `crashRatePercent`), `payload` (`launchAssetCount`, `averageUpdatePayloadBytes`), and a `daily[]` time series of `{ date, installs, failedInstalls }`.\n\nFor the complete schema and field reference, see [references\u002Fupdate-insights-schema.md](.\u002Freferences\u002Fupdate-insights-schema.md).\n\nFields that matter for health assessment:\n\n- `platforms[].totals.crashRatePercent`, computed as `failedInstalls \u002F (installs + failedInstalls) * 100`. Zero when there are no installs.\n- `platforms[].totals.installs` and `uniqueUsers` give the adoption signal.\n- `platforms[].daily` is a time series, useful for spotting a sudden spike in failures.\n\n### Errors\n\n- `Could not find any updates with group ID: \"\u003Cid>\"` — group doesn't exist or you lack access.\n- `Update group \"\u003Cid>\" has no ios update (available platforms: android)` — `--platform ios` was used but the group wasn't published for iOS.\n- `EAS Update insights is not supported by this version of eas-cli. Please upgrade ...` — the server deprecated a field the CLI relies on. Run `npm install -g eas-cli@latest`.\n\n## `eas update:view \u003CgroupId> --insights`\n\nExtends the standard `update:view` output with the same per-platform insights, inline.\n\n```bash\n# Human-readable\neas update:view 03d5dfcf-... --insights\neas update:view 03d5dfcf-... --insights --days 30\n\n# JSON: wrapped as { updates: [...], insights: {...} }\neas update:view 03d5dfcf-... --json --insights\n```\n\nWithout `--insights`, `update:view` behaves exactly as before — no JSON shape change for existing consumers. The `--days` \u002F `--start` \u002F `--end` flags only apply when `--insights` is set; passing them alone errors.\n\n## `eas channel:insights --channel \u003Cname> --runtime-version \u003Cversion>`\n\nShows, per channel, how many users are on the embedded build vs over-the-air updates and which updates are pulling the most traffic. Must be run from an Expo project directory.\n\n### Basic use\n\n```bash\neas channel:insights --channel production --runtime-version 1.0.6\n```\n\n### Flags\n\n| Flag | Description |\n|---|---|\n| `--channel \u003Cname>` | **Required.** The channel name (e.g. `production`, `staging`). |\n| `--runtime-version \u003Cversion>` | **Required.** Match exactly what was published. Check `runtimeVersion` values in `update:list`. |\n| `--days \u003CN>` | Look back N days. Default: **7**. |\n| `--start` \u002F `--end` | Explicit time range, like `update:insights`. |\n| `--json` \u002F `--non-interactive` | Machine-readable output. |\n\n### JSON output shape\n\nTop level: `channel`, `runtimeVersion`, `timespan`, `embeddedUpdateTotalUniqueUsers`, `otaTotalUniqueUsers`, `mostPopularUpdates[]` (each with `rank`, `groupId`, `message`, `platform`, `totalUniqueUsers`), `cumulativeMetricsAtLastTimestamp[]`, plus chart-shaped `uniqueUsersOverTime` and `cumulativeMetricsOverTime` objects with `labels` and `datasets`.\n\nFor the complete schema and field reference, see [references\u002Fchannel-insights-schema.md](.\u002Freferences\u002Fchannel-insights-schema.md).\n\nFields that matter:\n\n- `embeddedUpdateTotalUniqueUsers` is the count of users running the embedded (binary-bundled) build.\n- `mostPopularUpdates[]` is updates ranked by `totalUniqueUsers`. **Caveat**: this is the top-N the server returns; `otaTotalUniqueUsers` is a sum of that list and may undercount total OTA reach if more than top-N updates are active.\n- `uniqueUsersOverTime` and `cumulativeMetricsOverTime` are daily data series for charting.\n\n### Errors\n\n- `Could not find channel with the name \u003Cname>` — typo or wrong account.\n- \"No update launches recorded\" in the table \u002F empty `mostPopularUpdates` in JSON — no OTA update has been launched for that channel + runtime yet. Usually means the channel is still serving the embedded build only.\n\n## Common workflows\n\n### Verify the update I just published is healthy\n\n```bash\n# 1. Grab the latest publish on production\nGROUP_ID=$(eas update:list --branch production --json --non-interactive \\\n  | jq -r '.currentPage[0].group')\n\n# 2. Give it some adoption time (minutes to hours), then check crash rate\neas update:insights \"$GROUP_ID\" --json --non-interactive \\\n  | jq '.platforms[] | {platform, installs: .totals.installs, crashRate: .totals.crashRatePercent}'\n```\n\nCompare the `crashRate` across platforms and against previous releases; sudden spikes or asymmetric behaviour (iOS spiking while Android is flat, or vice versa) is the signal to investigate.\n\n### Compare adoption between two channels\n\n```bash\nfor channel in production staging; do\n  echo \"--- $channel ---\"\n  eas channel:insights --channel \"$channel\" --runtime-version 1.0.6 --json --non-interactive \\\n    | jq '{\n        channel,\n        embedded: .embeddedUpdateTotalUniqueUsers,\n        ota: .otaTotalUniqueUsers,\n        topUpdate: .mostPopularUpdates[0]\n      }'\ndone\n```\n\n### Detect a rollout regression in the last 24 hours\n\n```bash\neas update:insights \"$GROUP_ID\" --days 1 --json --non-interactive \\\n  | jq '.platforms[] | select(.totals.crashRatePercent > 1)'\n```\n\n### Summarize group metrics for release notes\n\n```bash\neas update:view \"$GROUP_ID\" --insights --days 30\n```\n\nHuman-readable group details plus 30 days of launches\u002Ffailures per platform — suitable for pasting into a changelog or incident review.\n\n## Output tips\n\n- Pipe JSON through `jq`; payloads are structured for easy filtering.\n- `--json` implies `--non-interactive`, but passing both is explicit and scripting-friendly.\n- Dates in `daily[].date` are UTC ISO timestamps; the human-readable table renders them as `YYYY-MM-DD` (UTC).\n- The CLI table labels say \"Launches\" \u002F \"Crashes\" while JSON uses `installs` \u002F `failedInstalls`. Same field, different display name.\n\n## Limitations\n\n- **Unique users across platforms** may double-count users who run the same publish on both iOS and Android. The same caveat applies to `otaTotalUniqueUsers` in channel insights, which is a sum over `mostPopularUpdates`.\n- **Fresh publishes** may show zeros for a short period while the metrics pipeline catches up.\n- **Installs are downloads, not launches**: the `installs` \u002F \"Launches\" field counts users who downloaded the manifest and launch asset. A confirmed run only registers on the user's *next* update check (typically up to 24h later, depending on the app's update policy). So metrics lag the real-world state slightly.\n- **Crashes are self-reported**: `failedInstalls` \u002F \"Crashes\" counts updates that errored during install\u002Flaunch and were reported on the next update check. Crashes that don't trigger an update request (e.g. process kill before recovery) won't appear.\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes @expo\u002Fagent-cli@latest feedback --category skills --subject \"eas-update-insights\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.\n",{"name":5,"license":14,"version":23,"description":7,"allowed-tools":24},"1.0.0","Bash(eas *)","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Feas-update-insights","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill eas-update-insights",{"tool":37,"command":38},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill eas-update-insights",{"tool":40,"command":41},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill eas-update-insights","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Feas-update-insights\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",394,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Feas-update-insights\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fchannel-insights-schema.md",2404,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Feas-update-insights\u002Freferences\u002Fchannel-insights-schema.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fupdate-insights-schema.md",2514,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fexpo\u002Fskills\u002Feas-update-insights\u002Freferences\u002Fupdate-insights-schema.md",[60,68,76,84,91,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]