eas-observe
An agent skill by expo, from expo/skills. Tags: analytics, cli, debugging, monitoring, performance, react-native.
What it does
EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC, markInteractive and ObserveInteractiveMarker, the useObserve hook, the Expo Router / React Navigation integrations for per-route metrics, user-defined events via `Observe.logEvent`, error reporting via ObserveErrorBoundary and `Observe.reportError`, and runtime config such as sampleRate and dispatchInDebug), querying via the EAS CLI (`eas observe:metrics-summary`, `observe:metrics`, `observe:routes`, `observe:events`, `observe:session`, `observe:versions`), interpreting the resulting metrics (cold/warm launch, TTR, TTI, navigation cold/warm TTR, update download, and the TTI frameRate/device/network params for triaging slow startups), or shipping an Observe integration inside a third-party package.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill eas-observe
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/eas-observe ~/.claude/skills/eas-observe
Safety box score
Grade D, elevated risk: 51 of 100 risk points, rated 2026-10-17. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill wires Expo EAS Observe into an app and uses the EAS CLI to read performance, error, and custom-event telemetry. Its main blast radius is external data flow: startup/navigation metrics, stack traces, route params, request metadata, and optional source maps can leave the device and be stored by Expo or a custom OTLP endpoint. It also asks you to run npm/EAS commands and edit app/build config files.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | The setup and feedback paths invoke external commands such as `npx expo install --fix`, `npx expo install expo-observe`, `eas build`, `eas update --upload-source-maps`, and `npx --yes submit-expo-feedback@latest`. |
| Network access | 3 (high) | The skill is built around sending telemetry off-device, and `references/setup.md` says "Network request monitoring is automatic and has no off switch" and that the custom endpoint is baked into the native build. |
| Filesystem reach | 2 (moderate) | Enabling Observe requires editing project files like `app/_layout.tsx` or `App.tsx`, `eas.json`, and app config (`extra.eas.observe.endpointUrl`), but the changes are scoped to the project. |
| Secrets & credentials | 2 (moderate) | The docs warn "Never put PII" in event data, and the telemetry can include route params, URLs, error stacks, and request-host metadata, so sensitive app data can be exported if the app passes it through. |
| Privilege & persistence | 0 (none) | No sudo, global installs, services, shell startup edits, or OS-level settings are requested. |
| Instruction hijack surface | 1 (low) | The docs include unattended examples such as `--non-interactive` and `--yes`, which can suppress prompts if followed verbatim, but they do not instruct the agent to ignore higher-priority rules. |
| Irreversible actions | 2 (moderate) | Using the skill can automatically dispatch telemetry and optionally publish source maps or feedback to Expo services, creating persistent external side effects beyond local inspection. |
| Transparency | 1 (low) | Most files are plain markdown, but `npx --yes submit-expo-feedback@latest` pulls and runs the latest registry package at runtime, which is not inspectable from this skill. |
Before installing
- Review `app/_layout.tsx` / `App.tsx`, `eas.json`, and app config diffs before enabling Observe.
- Decide whether you want `dispatchInDebug`, source-map upload, and custom endpoint settings before testing on real builds.
- Confirm your app will not emit secrets in `logEvent` attributes, route params, error messages, or request URLs.
- Avoid `npx --yes submit-expo-feedback@latest` unless you explicitly want to send feedback to Expo.
Rated 2026-10-17 by an automated review of 6 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/eas-observe/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- eas-update-insights — EAS service (paid). Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size.
- cpp-pro — Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques.
- database-optimizer — Optimizes database queries and improves performance across PostgreSQL and MySQL systems.
- embedded-systems — Use when developing firmware for microcontrollers, implementing RTOS applications, or optimizing power consumption.
- golang-pro — Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST.
- javascript-pro — Writes, debugs, and refactors JavaScript code using modern ES2023+ features, async/await patterns, ESM module systems.