Agent skill · software engineering · sickn33
expo-observe
Set up and query EAS Observe for Expo apps, including root integration, interactive markers, route metrics, CLI summaries, traces, logs, and performance diagnosis.
Why this skill is useful
Provides specific commands and integration patterns for querying and tracking metrics in Expo applications that the AI wouldn't reliably generate on its own.
What it needs
Requires expo-cli installed locally. About 1k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
EAS Observe When to Use Use this skill when you need use for anything related to EAS Observe — adding expo-observe to an Expo project (AppMetricsRoot/ObserveRoot HOC, markInteractive, the useObserve hook, and the Expo Router / React Navigation integrations for per-route metrics), querying via the EAS CLI (eas observe:metrics-summary,... 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+), and optional per-route navigation metrics through the Expo Router / React Navigation integrations. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/expo-observe--8cfc70