Instrument Expo apps with expo-observe and query performance metrics via the EAS CLI.
npx skills add https://github.com/bmiit145/leadBee --skill eas-observe-bmiit145
Please help me install this Agent Skill. Skill: eas-observe Source: https://github.com/bmiit145/leadBee/tree/main/mobile/.agents/skills/eas-observe Command: npx skills add https://github.com/bmiit145/leadBee --skill eas-observe-bmiit145
expo-observe to an Expo project with the correct SDK 55 vs SDK 56+ APIs (AppMetricsRoot/ObserveRoot, markInteractive, useObserve, ObserveInteractiveMarker), plus Expo Router and React Navigation integrations for per-route metrics. - CLI Querying: Run the six eas observe:* commands (metrics-summary, metrics, routes, events, session, versions) with correct flags, aliases, pagination, and JSON output shapes. - Metrics Interpretation: Diagnose cold/warm launch, TTR, and TTI using automatic frame-rate, device, and network params to distinguish main-thread contention from environmental throttling. - Use Case: After a release, run eas observe:metrics tti --sort slowest --days 7, grab a slow sample's sessionId, and replay the full session timeline to find the blocking request. ## Quick Start Ask the assistant to add EAS Observe instrumentation to your Expo app's root layout and mark the first screen interactive.High-intent search queries and answers about installing and using this skill.
Install expo-observe with npx expo install, wrap the root layout with AppMetricsRoot on SDK 55 or ObserveRoot on SDK 56+, then call markInteractive once the screen is usable. A development or production build is required since it does not work in Expo Go.
Use the six eas observe commands: metrics-summary for per-version aggregates, metrics for individual samples, routes for per-route navigation stats, events for custom logEvent data, session for a full session timeline, and versions for the app version hierarchy.
No. expo-observe is a native library and requires a development build or production build created with eas build. Metrics from debug builds are also not dispatched unless you set dispatchInDebug: true in configure().
High TTI with low frameRate.totalDelay means the launch sequence itself is long rather than janky. Check bundle size, data-fetch waterfalls, and initialization chains, and inspect the network request summary attached to the TTI event.
No. EAS Observe records unhandled JS errors, ObserveErrorBoundary render errors, and reportError calls as exception events, but it has no crash reporting. Use Sentry or BugSnag alongside it for native crash coverage.
EAS Observe is a paid EAS service. The free plan covers up to 10,000 monthly active users with limited features, and the server rejects queries your plan does not include with a plan-upgrade error.
trungenglishInstrument Expo apps with EAS Observe and query startup and navigation performance metrics.
tassiovaleAggregate crash rates, user adoption, and bundle size for EAS Updates.
NBXXFIntegrate Bugsnag error monitoring into the XXFTracker ecosystem.
golemcloudConfigure the golem-otlp-exporter plugin to export traces, logs, and metrics from Scala Golem agents.