About
This Claude Skill helps developers implement and analyze EAS Observe performance monitoring in Expo apps. It covers instrumentation with `expo-observe` for metrics like app launch (TTR/TTI) and navigation, plus querying data via EAS CLI commands. Use it to add performance tracking and diagnose slow startups using collected metrics.
Quick Install
Claude Code
Recommendednpx skills add expo/skills -a claude-code/plugin add https://github.com/expo/skillsgit clone https://github.com/expo/skills.git ~/.claude/skills/eas-observeCopy and paste this command in Claude Code to install this skill
Documentation
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 (AppMetricsRooton SDK 55,ObserveRooton SDK 56+), callmarkInteractive()(global on SDK 55, via theuseObserve()hook on SDK 56+), optional per-route navigation metrics through the Expo Router / React Navigation integrations, and user-defined events viaObserve.logEvent(SDK 56+). - Querying metrics from the terminal →
./references/queries.md. The fiveeas 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 TTIframeRate.*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/
GitHub Repository
Frequently asked questions
What is the eas-observe skill?
eas-observe is a Claude Skill by expo. Skills package instructions and resources that Claude loads on demand, so Claude can perform eas-observe-related tasks without extra prompting.
How do I install eas-observe?
Use the install commands on this page: add eas-observe to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does eas-observe belong to?
eas-observe is in the Design category, tagged react and ai.
Is eas-observe free to use?
Yes. eas-observe is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Related Skills
Use the executing-plans skill when you have a complete implementation plan to execute in controlled batches with review checkpoints. It loads and critically reviews the plan, then executes tasks in small batches (default 3 tasks) while reporting progress between each batch for architect review. This ensures systematic implementation with built-in quality control checkpoints.
This skill dispatches a code-reviewer subagent to analyze code changes against requirements before proceeding. It should be used after completing tasks, implementing major features, or before merging to main. The review helps catch issues early by comparing the current implementation with the original plan.
This skill provides a comprehensive guide for developers to connect MCP servers to Claude Code using HTTP, stdio, or SSE transports. It covers installation, configuration, authentication, and security for integrating external services like GitHub, Notion, and custom APIs. Use it when setting up MCP integrations, configuring external tools, or working with Claude's Model Context Protocol.
This skill helps developers choose between Claude Code Web and CLI interfaces based on task analysis, then enables seamless session teleportation between these environments. It optimizes workflow by managing session state and context when switching between web, CLI, or mobile. Use it for complex projects requiring different tools at various stages.
