[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A6J398JHV8M4WWHDPFEF5B":3,"skill-same:01M7A6J398JHV8M4WWHDPFEF5B":67},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7A6J398JHV8M4WWHDPFEF5B","eas-observe",null,"EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot\u002FObserveRoot HOC, markInteractive and ObserveInteractiveMarker, the useObserve hook, the Expo Router \u002F React Navigation integrations for per-route metrics, user-defined events via `Observe.logEvent`, error reporting via ObserveErrorBoundary and `Observe.reportError`, and runtime config such as sampleRate and dispatchInDebug), querying via the EAS CLI (`eas observe:metrics-summary`, `observe:metrics`, `observe:routes`, `observe:events`, `observe:session`, `observe:versions`), interpreting the resulting metrics (cold\u002Fwarm launch, TTR, TTI, navigation cold\u002Fwarm TTR, update download, and the TTI frameRate\u002Fdevice\u002Fnetwork params for triaging slow startups), or shipping an Observe integration inside a third-party package.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"MIT","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot\u002FObserveRoot HOC, markInteractive and ObserveInteractiveMarker, the useObserve hook, the Expo Router \u002F React Navigation integrations for per-route metrics, user-defined events via `Observe.logEvent`, error reporting via ObserveErrorBoundary and `Observe.reportError`, and runtime config such as sampleRate and dispatchInDebug), querying via the EAS CLI (`eas observe:metrics-summary`, `observe:metrics`, `observe:routes`, `observe:events`, `observe:session`, `observe:versions`), interpreting the resulting metrics (cold\u002Fwarm launch, TTR, TTI, navigation cold\u002Fwarm TTR, update download, and the TTI frameRate\u002Fdevice\u002Fnetwork params for triaging slow startups), or shipping an Observe integration inside a third-party package.\"\nlicense: \"MIT\"\n---\n# EAS Observe\n\n> **EAS service - costs apply.** EAS Observe is an Expo Application Services product. The free EAS plan allows up to 10,000 monthly active users, with a limited set of features; higher usage requires a paid subscription. For details, see https:\u002F\u002Fexpo.dev\u002Fpricing#plan-features.\n\nEAS Observe tracks startup, navigation, and custom-event performance from production Expo apps. It needs a development or production build — the native library is not in Expo Go.\n\n> **Source of truth:** https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002F — always consult the canonical docs when API details matter, especially get-started, configuration, integrations, and the metrics reference. EAS Observe is evolving; this skill's references are written to stay accurate but may lag the docs.\n\n## Which reference to read\n\nThe four reference files in `.\u002Freferences\u002F` cover what people typically need this skill for:\n\n- **Adding EAS Observe to a project** → [`.\u002Freferences\u002Fsetup.md`](.\u002Freferences\u002Fsetup.md). Install, wrap the root layout (`AppMetricsRoot` on SDK 55, `ObserveRoot` on SDK 56+), mark the app interactive (global `markInteractive()` on SDK 55, the `useObserve()` hook or `\u003CObserveInteractiveMarker \u002F>` on SDK 56+), optional per-route navigation metrics through the Expo Router \u002F React Navigation integrations, user-defined events via `Observe.logEvent` (SDK 56+), error reporting, and runtime configuration (sampling, dispatch, environments, custom endpoint).\n- **Querying metrics from the terminal** → [`.\u002Freferences\u002Fqueries.md`](.\u002Freferences\u002Fqueries.md). The six `eas observe:*` commands — `metrics-summary`, `metrics`, `routes`, `events`, `session`, `versions` — with flags, metric aliases, table layouts, JSON shapes, and common workflows.\n- **Reading a dashboard or CLI output** → [`.\u002Freferences\u002Fmetrics.md`](.\u002Freferences\u002Fmetrics.md). Target thresholds per metric, what the automatic TTI params mean (`frameRate.*`, `device.*`, `network.*`), and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention, hard blocks, or throttled devices.\n- **Shipping an Observe integration in a library** → [`.\u002Freferences\u002Fthird-party.md`](.\u002Freferences\u002Fthird-party.md). For package authors only (SDK 57+): optional peer dependency, config declaration merging, `Observe.registerIntegration()`, and event naming.\n\n## Quick links to the docs\n\n- Get started: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fget-started\u002F\n- Dashboard guide: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fdashboard\u002F\n- Querying with EAS CLI: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Feas-cli\u002F\n- Metrics reference: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Freference\u002Fmetrics\u002F\n- Expo Router integration: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fintegrations\u002Fexpo-router\u002F\n- React Navigation integration: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fintegrations\u002Freact-navigation\u002F\n- User-defined events: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fevents\u002F\n- Configuration: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fconfiguration\u002F\n- Third-party integrations: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fintegrations\u002Fthird-party\u002F\n- EAS Update download performance: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Feas-update\u002F\n- Troubleshooting: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Freference\u002Ftroubleshooting\u002F\n\n## Known gaps between the docs and the shipped code\n\nVerified against `eas-cli` 21.8.0 and `expo-observe` 57.0.9. Trust this skill's references over the docs on these points, but re-check with `--help` and the installed package before relying on them:\n\n- All six CLI commands are on the [Querying with EAS CLI](https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Feas-cli\u002F) page. Older doc builds list only four and omit `observe:routes` and `observe:session`.\n- Navigation metric aliases are `nav_cold_ttr`, `nav_warm_ttr`, and `nav_tti`. There are no bare `cold_ttr` \u002F `warm_ttr` aliases in the CLI.\n- Sorting uses `--sort \u003Cslowest|fastest|newest|oldest>`. There is no `--order` flag.\n- `ObserveErrorBoundary`, `Observe.reportError`, and `configure({ errorHandlingEnabled })` are exported but undocumented. Observe still has no crash reporting; use Sentry or BugSnag for that.\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 submit-expo-feedback@latest --category skills --subject \"eas-observe\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n","# EAS Observe\n\n> **EAS service - costs apply.** EAS Observe is an Expo Application Services product. The free EAS plan allows up to 10,000 monthly active users, with a limited set of features; higher usage requires a paid subscription. For details, see https:\u002F\u002Fexpo.dev\u002Fpricing#plan-features.\n\nEAS Observe tracks startup, navigation, and custom-event performance from production Expo apps. It needs a development or production build — the native library is not in Expo Go.\n\n> **Source of truth:** https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002F — always consult the canonical docs when API details matter, especially get-started, configuration, integrations, and the metrics reference. EAS Observe is evolving; this skill's references are written to stay accurate but may lag the docs.\n\n## Which reference to read\n\nThe four reference files in `.\u002Freferences\u002F` cover what people typically need this skill for:\n\n- **Adding EAS Observe to a project** → [`.\u002Freferences\u002Fsetup.md`](.\u002Freferences\u002Fsetup.md). Install, wrap the root layout (`AppMetricsRoot` on SDK 55, `ObserveRoot` on SDK 56+), mark the app interactive (global `markInteractive()` on SDK 55, the `useObserve()` hook or `\u003CObserveInteractiveMarker \u002F>` on SDK 56+), optional per-route navigation metrics through the Expo Router \u002F React Navigation integrations, user-defined events via `Observe.logEvent` (SDK 56+), error reporting, and runtime configuration (sampling, dispatch, environments, custom endpoint).\n- **Querying metrics from the terminal** → [`.\u002Freferences\u002Fqueries.md`](.\u002Freferences\u002Fqueries.md). The six `eas observe:*` commands — `metrics-summary`, `metrics`, `routes`, `events`, `session`, `versions` — with flags, metric aliases, table layouts, JSON shapes, and common workflows.\n- **Reading a dashboard or CLI output** → [`.\u002Freferences\u002Fmetrics.md`](.\u002Freferences\u002Fmetrics.md). Target thresholds per metric, what the automatic TTI params mean (`frameRate.*`, `device.*`, `network.*`), and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention, hard blocks, or throttled devices.\n- **Shipping an Observe integration in a library** → [`.\u002Freferences\u002Fthird-party.md`](.\u002Freferences\u002Fthird-party.md). For package authors only (SDK 57+): optional peer dependency, config declaration merging, `Observe.registerIntegration()`, and event naming.\n\n## Quick links to the docs\n\n- Get started: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fget-started\u002F\n- Dashboard guide: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fdashboard\u002F\n- Querying with EAS CLI: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Feas-cli\u002F\n- Metrics reference: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Freference\u002Fmetrics\u002F\n- Expo Router integration: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fintegrations\u002Fexpo-router\u002F\n- React Navigation integration: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fintegrations\u002Freact-navigation\u002F\n- User-defined events: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fevents\u002F\n- Configuration: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fconfiguration\u002F\n- Third-party integrations: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Fintegrations\u002Fthird-party\u002F\n- EAS Update download performance: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Feas-update\u002F\n- Troubleshooting: https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Freference\u002Ftroubleshooting\u002F\n\n## Known gaps between the docs and the shipped code\n\nVerified against `eas-cli` 21.8.0 and `expo-observe` 57.0.9. Trust this skill's references over the docs on these points, but re-check with `--help` and the installed package before relying on them:\n\n- All six CLI commands are on the [Querying with EAS CLI](https:\u002F\u002Fdocs.expo.dev\u002Feas\u002Fobserve\u002Feas-cli\u002F) page. Older doc builds list only four and omit `observe:routes` and `observe:session`.\n- Navigation metric aliases are `nav_cold_ttr`, `nav_warm_ttr`, and `nav_tti`. There are no bare `cold_ttr` \u002F `warm_ttr` aliases in the CLI.\n- Sorting uses `--sort \u003Cslowest|fastest|newest|oldest>`. There is no `--order` flag.\n- `ObserveErrorBoundary`, `Observe.reportError`, and `configure({ errorHandlingEnabled })` are exported but undocumented. Observe still has no crash reporting; use Sentry or BugSnag for that.\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 submit-expo-feedback@latest --category skills --subject \"eas-observe\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n",{"license":15,"description":7},"main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Feas-observe","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add NeelakshSaxena\u002FVayu --skill eas-observe",{"tool":37,"command":38},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill eas-observe",{"tool":40,"command":41},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill eas-observe","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",467,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fmetrics.md",8755,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002Freferences\u002Fmetrics.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fqueries.md",17904,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002Freferences\u002Fqueries.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fsetup.md",23818,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002Freferences\u002Fsetup.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fthird-party.md",4666,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Feas-observe\u002Freferences\u002Fthird-party.md",[68,76,83,90,97,104],{"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":72,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\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":72,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]