mcpField
E
expo-observe

expo-observe

github.com/expoDevelopment3.5k6.2k installsUpdated today
Repository

About expo-observe

A skill for Expo developers integrating EAS Observe and inspecting production performance data. It covers setup, navigation and custom events, CLI queries, and metric interpretation.

Key features

  1. 01Integrate EAS Observe
  2. 02Track startup and navigation metrics
  3. 03Record custom events
  4. 04Query performance data with the CLI
  5. 05Interpret metrics and diagnostic patterns

Use cases

  1. 01Set up production performance monitoring for an Expo app
  2. 02Inspect metrics, routes, and events from the terminal
  3. 03Identify slow startup or main-thread contention from metrics

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/expo/skills --skill expo-observe

After installing, type/expo-observein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
metrics.md
queries.md
setup.md

Details

From the project README

EAS Observe

EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps.

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.

Which reference to read

The three reference files in ./references/ cover the three things people typically need this skill for:

  • Adding EAS Observe to a project → ./references/setup.md. Install, wrap the root layout (AppMetricsRoot on SDK 55, ObserveRoot on SDK 56+), call markInteractive() (global on SDK 55, via the useObserve() hook on SDK 56+), optional per-route navigation metrics through the Expo Router / React Navigation integrations, and user-defined events via Observe.logEvent (SDK 56+).
  • Querying metrics from the terminal → ./references/queries.md. The five eas observe:* commands — metrics-summary, metrics, routes, events, versions — with flags, table layouts, JSON shapes, and common workflows.
  • Reading a dashboard or CLI output → ./references/metrics.md. Target thresholds per metric, what the TTI frameRate.* params mean, and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention or hard blocks.

Quick links to the docs

Comments

Markdown supported