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

Get started: https://docs.expo.dev/eas/observe/get-started/
Dashboard guide: https://docs.expo.dev/eas/observe/dashboard/
Metrics reference: https://docs.expo.dev/eas/observe/reference/metrics/
Expo Router integration: https://docs.expo.dev/eas/observe/integrations/expo-router/
React Navigation integration: https://docs.expo.dev/eas/observe/integrations/react-navigation/
User-defined events: https://docs.expo.dev/eas/observe/events/
Configuration: https://docs.expo.dev/eas/observe/configuration/

Files5

5 files · 30.4 KB

Select a file to preview

Overall Score

87/100

Grade

A

Excellent

Safety

90

Quality

85

Clarity

88

Completeness

83

Summary

EAS Observe is a reference skill that guides agents to add expo-observe instrumentation to Expo projects, query performance metrics via the EAS CLI, and interpret cold/warm launch, TTR, and TTI results. It provides three detailed reference guides (setup, CLI queries, and metrics interpretation) plus links to official Expo documentation.

Static Analysis Findings

1 finding

Patterns detected by deterministic static analysis before AI scoring. Hover over any finding code for detailed information and remediation guidance.

Credential Exposure

SEC-020Direct .env File Access

Direct .env file access

references/metrics.md.env

85% confidenceCWE-538: Sensitive Info in Externally-Accessible File

Detected Capabilities

Code example generationReference documentationFile write guidance (React/TypeScript)Terminal command referenceMetrics interpretation

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

add expo-observeeas observe clistartup performance metricstime to interactivenavigation metricscustom events loggingapp performanceeas observe:routes

Risk Signals

INFO

References .env file in metrics.md (dispatch caveats section)

references/metrics.md

Referenced Domains

External domains referenced in skill content, detected by static analysis.

docs.expo.devexpo.dev

Use Cases

Add expo-observe to an Expo app (SDK 55 or 56+) and wrap the root layout
Call markInteractive() to measure Time To Interactive (TTI)
Enable per-route/per-screen navigation metrics with Expo Router or React Navigation
Emit custom user-defined events via Observe.logEvent for product analytics
Query app startup metrics from the terminal with eas observe:metrics-summary
Query individual performance samples with eas observe:metrics or eas observe:routes
Interpret TTI frameRate params to diagnose slow startup (main-thread contention vs. smooth-but-slow)
Filter metrics by app version, platform, time range, and custom update IDs

Quality Notes

Well-structured with clear SDK 55 vs 56+ versioning tables and conditional guidance
Comprehensive code examples for every setup step, with and without Expo Router
Excellent CLI command reference with full flag documentation, common workflows, and JSON output shapes
Metrics interpretation includes diagnostic patterns (main-thread contention vs. frozen frames) with actionable examples
All three reference files are complete and internally cross-referenced
Explicitly documents that this is a paid EAS service with free-tier limits
Clear prerequisite checks and quick-checklist for verification
Canonical docs links provided throughout for latest API changes

Model: claude-haiku-4-5-20251001Analyzed: Jul 11, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

eas-observe