Home/Mobile/eas-observe
E

eas-observe

by @expov
4.6(120)

This skill integrates EAS Observe into Expo projects, automatically tracking startup, navigation, and custom event performance, and querying metrics via EAS CLI or interpreting dashboard data to quickly diagnose bottlenecks in cold/warm launches, navigation transitions, and user-defined events for optimized user experience.

easexpoperformancemonitoringmobileGitHub
Installation
npx skills add https://github.com/expo/skills --skill eas-observe
compare_arrows

Before / After Comparison

1 组
Before

Without this skill, developers manually analyze startup performance by writing custom logs and repeating tests, taking hours and often missing key metrics to identify slow startup causes.

After

With this skill, key metrics like cold/warm launch, TTI are automatically collected and visualized via CLI or dashboard, reducing diagnosis time to minutes and supporting breakdowns by version and route.

SKILL.md

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.

User Reviews (0)

Write a Review

Effect
Usability
Docs
Compatibility

No reviews yet

Statistics

Installs18.6K
Rating4.6 / 5.0
Version
Updated2026年10月23日
Comparisons1

User Rating

4.6(120)
5
37%
4
43%
3
13%
2
5%
1
2%

Rate this Skill

0.0

Compatible Platforms

🤖claude-code

Timeline

Created2026年7月26日
Last Updated2026年10月23日
🎁 Agent Knowledge Cards
Survey