Update to Expo2

{
  "description": "Set up expo-observe and query EAS Observe metrics. Use for startup, launch, and navigation performance (TTR, TTI), custom events, error reporting, sampling configuration, expo-image and Reanimated integrations, CLI or Expo MCP queries, or Observe integrations in libraries. For published OTA-update health and adoption, use eas-update-insights.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 470
    },
    {
      "relative_path": "references/library-integrations.md",
      "size_in_bytes": 6922
    },
    {
      "relative_path": "references/metrics.md",
      "size_in_bytes": 8755
    },
    {
      "relative_path": "references/queries.md",
      "size_in_bytes": 24330
    },
    {
      "relative_path": "references/setup.md",
      "size_in_bytes": 28146
    },
    {
      "relative_path": "references/third-party.md",
      "size_in_bytes": 4666
    }
  ],
  "name": "eas-observe",
  "skill_md_contents": "---\nname: eas-observe\ndescription: Set up expo-observe and query EAS Observe metrics. Use for startup, launch, and navigation performance (TTR, TTI), custom events, error reporting, sampling configuration, expo-image and Reanimated integrations, CLI or Expo MCP queries, or Observe integrations in libraries. For published OTA-update health and adoption, use eas-update-insights.\nlicense: MIT\n---\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://expo.dev/pricing#plan-features.\n\nEAS Observe tracks startup, navigation, and custom-event performance from production Expo apps, and records JavaScript errors and native crashes. It needs a development or production build — the native library is not in Expo Go.\n\n> **Source of truth:** https://docs.expo.dev/eas/observe/ — 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 five reference files in `./references/` cover what people typically need this skill for:\n\n- **Adding EAS Observe to a project** → [`./references/setup.md`](./references/setup.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 `<ObserveInteractiveMarker />` on SDK 56+), optional per-route navigation metrics through the Expo Router / 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** → [`./references/queries.md`](./references/queries.md). The `npx --yes eas-cli@27.4.1 observe:*` commands — `metrics-summary`, `metrics`, `routes`, `events`, `session`, `versions`, `errors`, `event` — with flags, metric aliases, table layouts, JSON shapes, and common workflows. Also the matching `observe_*` tools in the Expo MCP Server, and how their inputs differ from the CLI flags.\n- **Reading a dashboard or CLI output** → [`./references/metrics.md`](./references/metrics.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- **Reporting problems from library integrations** → [`./references/library-integrations.md`](./references/library-integrations.md). The current and future integrations that report problems a library detects as events or errors, with their options, limits, and how to query the reports. Currently: `expo-image` (`expo-image.oversized` events for images decoded far larger than the screen) and `react-native-reanimated` (`reanimated.error` errors and optional `reanimated.warning` events).\n- **Shipping an Observe integration in a library** → [`./references/third-party.md`](./references/third-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://docs.expo.dev/eas/observe/get-started/\n- Dashboard guide: https://docs.expo.dev/eas/observe/dashboard/\n- Querying with EAS CLI: https://docs.expo.dev/eas/observe/eas-cli/\n- Querying with the Expo MCP Server: https://docs.expo.dev/eas/observe/mcp/\n- Metrics reference: https://docs.expo.dev/eas/observe/reference/metrics/\n- Expo Router integration: https://docs.expo.dev/eas/observe/integrations/expo-router/\n- React Navigation integration: https://docs.expo.dev/eas/observe/integrations/react-navigation/\n- Expo Image integration: https://docs.expo.dev/eas/observe/integrations/expo-image/\n- Reanimated integration: https://docs.expo.dev/eas/observe/integrations/react-native-reanimated/\n- User-defined events: https://docs.expo.dev/eas/observe/events/\n- Error reporting: https://docs.expo.dev/eas/observe/errors/\n- Configuration: https://docs.expo.dev/eas/observe/configuration/\n- Third-party integrations: https://docs.expo.dev/eas/observe/integrations/third-party/\n- EAS Update download performance: https://docs.expo.dev/eas/observe/eas-update/\n- Troubleshooting: https://docs.expo.dev/eas/observe/reference/troubleshooting/\n\n## Submitting Feedback\nWhen the user requests feedback submission, use:\n```bash\nnpx --yes @expo/agent-cli@1.0.23 feedback --category skills --subject \"eas-observe\" \"<actionable feedback>\"\n```\nInclude only relevant technical details; keep credentials, private data, and conversation contents out of feedback.\n"
}