New to Claude Skills? Learn how to install them →

Get Claude Skills
expo on GitHub

EAS Observe

Free

Track and analyze performance metrics for Expo apps.

by expo2.4k stars on expo/skills
1 views
Updated Aug 7, 2026
Get this skill

Free · Opens the source repo

What EAS Observe does

EAS Observe is a service designed for developers using Expo to monitor the performance of their applications. It provides tools to track startup times, navigation metrics, and custom events, allowing you to gain insights into app performance in real-time. By integrating EAS Observe into your Expo project, you can utilize components like AppMetricsRoot or ObserveRoot to wrap your application, enabling automatic performance tracking and logging of user-defined events through the Observe.logEvent function.

The skill includes essential commands for querying metrics via the EAS CLI, such as eas observe:metrics-summary, which gives a high-level overview of your app's performance, or eas observe:events, which allows you to delve into specific user interactions. Understanding these metrics is crucial for diagnosing issues like slow startups, as EAS Observe provides detailed insights into cold/warm launches, time-to-interactive (TTI), and navigation performance. This helps developers identify bottlenecks and optimize the user experience effectively.

EAS Observe is particularly beneficial for developers looking to enhance the performance of their Expo applications. It is suitable for both new projects and existing apps that require performance monitoring. The service is a paid offering with a free-tier limit, so it's essential to review the pricing details before deploying it in a production environment. By leveraging EAS Observe, developers can ensure their applications provide a smooth user experience, which is vital for user retention and satisfaction.

When to use it

Use EAS Observe when you need to monitor the performance metrics of your Expo applications, especially in production environments.

When not to use it

This skill may not be suitable for projects that do not utilize Expo or for developers who are not interested in performance metrics.

What you can build with it

Integrating EAS Observe in a New Expo Project

When starting a new Expo project, you can implement EAS Observe to track performance metrics from the outset, ensuring you have insights from the beginning.

Monitoring Performance in a Production App

For an existing Expo app in production, use EAS Observe to gather real-time metrics and identify performance bottlenecks affecting user experience.

Analyzing User Interaction Events

If you want to understand user behavior within your app, EAS Observe allows you to log custom events and analyze their impact on app performance.

How to install EAS Observe

View source

1. Install with the skills CLI

npx skills add expo/skills/eas-observe --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by expo

EAS Observe

EAS service - costs apply. EAS Observe is a paid Expo Application Services product with free-tier limits. Ingesting and querying production metrics counts against your plan's event/usage allowance. Review https://expo.dev/pricing before enabling it in production.

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

Submitting Feedback

If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:

npx --yes submit-expo-feedback@latest --category skills --subject "eas-observe" "<actionable feedback>"

Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If 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.

Frequently asked questions about EAS Observe

Similar skills

Heap Snapshot Analysis

Investigate V8 heap snapshots for memory issues.

VS Code Performance Workflow

Automate performance investigations in VS Code.

Memory Leak Audit

Prevent memory leaks with effective coding patterns.

CPU Profile Analysis

Analyze V8 and Chrome performance profiles for optimization.

Chat Performance Testing

Benchmark and validate chat UI performance in VS Code.

Vercel React Best Practices

Optimize your React and Next.js applications for performance.