[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPJMHDYCK467AJS87BMFQK":3,"skill-same:01M7CPJMHDYCK467AJS87BMFQK":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CPJMHDYCK467AJS87BMFQK","eas-update-insights",null,"Check the health of published EAS Updates: 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.","peterish8\u002Fprats-skill-atlas","peterish8","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F181628466?v=4","01M7CHQAPN6X8D29E2Q8DW4BYF","Prathick Dhanes R","01M7CHQAQ7T42E6D8HH3CZH342",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fother\u002Funcategorized\u002Feas-update-insights\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: eas-update-insights\ndescription: \"Check the health of published EAS Updates: 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\nQuery 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.\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","# EAS Update Insights\n\nQuery 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.\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",{"name":5,"license":15,"version":24,"description":7,"allowed-tools":25},"1.0.0","Bash(eas *)","main","f1bcf88a052c2ccbb297666b33fb820cfd94ac71",".claude\u002Fskills\u002Fother\u002Funcategorized\u002Feas-update-insights",0,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas","https:\u002F\u002Fgithub.com\u002Fpeterish8","Building real-world products with clean UI, smart architecture, and privacy in mind. Frontend-focused, full-stack curious.","2026-10-15 19:02:31",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add peterish8\u002Fprats-skill-atlas --skill eas-update-insights",{"tool":40,"command":41},"bunx","bunx skills add peterish8\u002Fprats-skill-atlas --skill eas-update-insights",{"tool":43,"command":44},"pnpm","pnpm dlx skills add peterish8\u002Fprats-skill-atlas --skill eas-update-insights","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fother\u002Funcategorized\u002Feas-update-insights\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fchannel-insights-schema.md","REFERENCE","参考文档",2404,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fother\u002Funcategorized\u002Feas-update-insights\u002Freferences\u002Fchannel-insights-schema.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fupdate-insights-schema.md",2514,"https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fother\u002Funcategorized\u002Feas-update-insights\u002Freferences\u002Fupdate-insights-schema.md",[59,68,76,84,91,99],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7CTAZW9MHV3RWH2ZEKDQXG9","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftools-utilities\u002Fgeneral-purpose\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CT8MG7NB1JR67XYZ9EWW3B","seo-audit","Full website SEO audit with parallel subagent delegation. Crawls up to 500 pages, detects business type, delegates to up to 15 specialists (8 always + 7 conditional), generates health score. Use when user says audit, full SEO check, analyze my site, or website health check.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fseo-audit\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":63,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CT87F6GQ0WAD393PKPAGGX","playwright","Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via `playwright-cli` or the bundled wrapper script.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fplaywright\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CT809RF90MG98MYEA97D8Z","gsap-performance","Official GSAP skill for performance — prefer transforms, avoid layout thrashing, will-change, batching. Use when optimizing GSAP animations, reducing jank, or when the user asks about animation performance, FPS, or smooth 60fps.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Fgsap-performance\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CT7Q4VD995JHZMQQFBZZV9","firecrawl-seo-audit","Audit a website's SEO with Firecrawl. Use when the user asks for an SEO audit, metadata and heading review, sitemap\u002Fsite-structure analysis, keyword opportunities, competitor SERP comparison, or prioritized search optimization recommendations.","ISC","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-seo-audit\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":95,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CT7JRJFC5RAKJBAP0VS1CV","firecrawl-qa","QA test a live website with Firecrawl browser and scrape evidence. Use when the user wants exploratory QA, form testing, navigation\u002Flink checks, responsive checks, performance observations, bug reports, or a pre-launch quality review.","https:\u002F\u002Fgithub.com\u002Fpeterish8\u002Fprats-skill-atlas\u002Fblob\u002Fmain\u002F.codex\u002Fskills\u002Ftesting\u002Fqa-and-verification\u002Ffirecrawl-qa\u002FSKILL.md",[],[]]