PlugWiki

EAS Observe Skill from Expo: Add and Read App Performance Metrics

eas-observe is the official Expo skill that helps Claude add performance tracking to an Expo app, then read launch, route and error numbers from the terminal.

Installs
20.7K
on skills.sh
Stars
4K
on GitHub
Files
6
besides SKILL.md
Updated
Nov 2026
last repo commit

The skill covers three jobs. It adds the expo-observe library to an Expo project, with the root wrapper, the "app is interactive" marker, optional per-route metrics, custom events and error reporting. It queries results with eas observe:* commands or the Expo tool server's observe_* tools. And it explains what the numbers mean, such as cold and warm launch, TTR and TTI.

Five reference files hold the detail: setup, queries, metrics, library integrations and third-party integrations. SKILL.md names a source-of-truth docs site and warns that the skill may lag it.

SKILL.md opens with a cost note. EAS Observe is an Expo Application Services product. The free plan allows up to 10,000 monthly active users with limited features, and higher usage needs a paid plan. It needs a development or production build, not Expo Go, and an Expo account.

Good for

  • Expo and React Native developers who want production startup and navigation metrics
  • Teams triaging slow app launches or JavaScript errors from real users
  • Library authors who want to ship an Observe integration in their package

Install eas-observe

Claude Code

  1. 1

    Copy this prompt.

    Install the eas-observe skill in Claude Code. Run this command:

claude plugin install expo@claude-plugins-official

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

The plugin installs all 23 Expo skills and also registers the Expo tool server at https://mcp.expo.dev/mcp. The skills CLI command installs only eas-observe.

From the project README. Source.

What's in the skill

When it loads

Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC, markInteractive and ObserveInteractiveMarker, the useObserve hook, the Expo Router / React Navigation integrations for per-route metrics, the expo-image and Reanimated integrations, user-defined events via `Observe.logEvent`, error reporting via ObserveErrorBoundary and `Observe.reportError`, native crash reporting, source map upload for symbolicated stack traces, 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`, `observe:errors`, `observe:event`) or the Expo MCP `observe_*` tools, interpreting the resulting metrics (cold/warm launch, TTR, TTI, navigation cold/warm TTR, update download, and the TTI frameRate/device/network params for triaging slow startups), or shipping an Observe integration inside a third-party package.

Sections in SKILL.md

  1. Which reference to read
  2. Quick links to the docs
  3. Submitting Feedback

Key facts

Author
Expo (GitHub: expo)
Repo
expo/skills
Installs on skills.sh
20,692 as of 2026-11-02
GitHub stars (whole repo)
4,005 as of 2026-11-02
License
MIT
Last repo commit
2026-11-01
Files in the skill folder
7 files including SKILL.md
skills.sh audits
Gen Agent Trust Hub pass, Socket pass, Snyk pass

What it includes

  • Install expo-observe, wrap the root, mark interactive

    Steps for SDK 55 (AppMetricsRoot, global markInteractive) and SDK 56+ (ObserveRoot, useObserve hook). Also covers router integrations, events, error reporting, source maps and runtime config.

    Runs code · references/setup.md

  • eas observe commands and the matching MCP tools

    Eight commands: metrics-summary, metrics, routes, events, session, versions, errors and event. Includes flags, metric aliases and JSON shapes.

    Runs code · references/queries.md

  • Read launch and TTI numbers and triage slow starts

    Target thresholds per metric and what the frame rate, device and network parameters mean.

    references/metrics.md

  • expo-image and Reanimated problem reports

    Covers expo-image oversized-image events and Reanimated errors and warnings.

    references/library-integrations.md

  • Ship an Observe integration in a library (SDK 57+)

    For package authors: optional peer dependency, registerIntegration and event naming.

    references/third-party.md

  • Optionally report skill errors to Expo

    SKILL.md includes an npx command that sends feedback to Expo through @expo/agent-cli.

    Runs code · Feedback command

From the official docs

Permissions

Medium risk

The skill makes Claude add telemetry code to your app and run npx and eas commands, and the data leaves the device once the app ships. Review the changes and the privacy impact before you release a build.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • Your app starts sending performance data

    expo-observe sends launch, route, event and error data from production builds. The setup guide says network request hosts leave the device and cannot be switched off as of expo-observe 57.0.9. github.com

  • It runs installs and builds on your project

    The setup guide uses npx expo install, eas build and eas update commands. Review each command before you approve it. github.com

  • The Expo plugin adds a tool server

    The plugin route also registers the Expo tool server at https://mcp.expo.dev/mcp and installs 23 skills. The skills CLI route installs only this skill. github.com

  • It can send feedback to Expo

    SKILL.md includes an npx @expo/agent-cli feedback command, to be used only for specific, actionable reports. Decline it if you do not want to send anything. github.com

Technical details
Talks toEAS Observe service (or your custom endpoint). https://mcp.expo.dev/mcp (if you install the plugin)
Sign-in and keysNot stated in SKILL.md; the setup guide lists an Expo account as a prerequisite.
Scopes

  • your Expo project

  • EAS project

Questions

What does the EAS Observe skill do?

It helps Claude add expo-observe to an Expo app, query the collected metrics with the EAS CLI or the Expo tool server, and interpret launch, navigation and error data.

How do I install it in Claude Code or Codex?

Use the install box above. The Expo README recommends its plugin for Claude Code and Codex, which installs all Expo skills. The skills CLI command installs only this one.

Is EAS Observe free?

Partly. SKILL.md says the free EAS plan allows up to 10,000 monthly active users with a limited set of features, and higher usage needs a paid subscription. Check Expo's pricing page for current terms.

Does it need an account or API key?

The setup guide lists an Expo account, Expo SDK 55 or later, an EAS project and a development or production build as prerequisites. It does not work in Expo Go.

Is it safe to install?

The skill is markdown and one small YAML file, with no bundled scripts. It does lead Claude to change your app code, run npx and eas commands, and add telemetry that sends data from your app, so read the diff before you build.

Can I send the data somewhere other than Expo?

Yes. The setup guide describes a custom endpoint that takes OpenTelemetry data over HTTP, set in the app config. You must rebuild the native app after changing it.

Information

updated Nov 2, 2026

Repository
expo/skills
Folder
plugins/expo/skills/eas-observe

expo/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 6
  1. expo/skills README · github.com
  2. expo plugin .mcp.json · github.com
  3. skills.sh listing · skills.sh
  4. eas-observe SKILL.md · github.com
  5. eas-observe setup.md · github.com
  6. eas-observe queries.md · github.com

Updated Nov 2, 2026.