SkillAgentSearch skills...

eas-observe

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, the expo-image and Reanimated integrations, us…

Install / Use

npx skills add expo/skills --skill eas-observe

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Marketing

Supported Platforms

Universal

Our assessment of eas-observe

eas-observe scores 85/100 on our quality scale, 426th of 642 Marketing skills we index.

Its SKILL.md is 5.4 KB long, split into 5 sections with 1 code example: a solid amount of guidance for an agent.

With 2,602 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so eas-observe is actively maintained.
  • Our last check on 2026-11-04 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

eas-observe compared with similar skills

All 4 of these similar skills score higher than eas-observe; compare them before choosing.

SkillScoreStarsUpdatedFormat
eas-observe (this skill)by expo852.6k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
LocalAIby mudler10050.4ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install eas-observe?
Run npx skills add expo/skills --skill eas-observe. The install tabs above show the steps for each supported agent.
Which AI agents does eas-observe work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is eas-observe safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is eas-observe still maintained?
The repository was last updated about 2 months ago, so eas-observe is actively maintained.

name: eas-observe description: 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. version: 1.1.0 license: MIT

EAS Observe

EAS service - costs apply. EAS Observe is an Expo Application Services product. The free EAS plan allows up to 10,000 monthly active users, with a limited set of features; higher usage requires a paid subscription. For details, see https://expo.dev/pricing#plan-features.

EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps. It needs a development or production build — the native library is not in Expo Go.

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 four reference files in ./references/ cover what 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+), mark the app interactive (global markInteractive() on SDK 55, the useObserve() hook or <ObserveInteractiveMarker /> on SDK 56+), optional per-route navigation metrics through the Expo Router / React Navigation integrations, user-defined events via Observe.logEvent (SDK 56+), error reporting, and runtime configuration (sampling, dispatch, environments, custom endpoint).
  • Querying metrics from the terminal → ./references/queries.md. The six eas observe:* commands — metrics-summary, metrics, routes, events, session, versions — with flags, metric aliases, table layouts, JSON shapes, and common workflows.
  • Reading a dashboard or CLI output → ./references/metrics.md. Target thresholds per metric, what the automatic TTI params mean (frameRate.*, device.*, network.*), and diagnostic patterns for telling slow-but-smooth startup apart from main-thread contention, hard blocks, or throttled devices.
  • Shipping an Observe integration in a library → ./references/third-party.md. For package authors only (SDK 57+): optional peer dependency, config declaration merging, Observe.registerIntegration(), and event naming.

Quick links to the docs

  • Get started: https://docs.expo.dev/eas/observe/get-started/
  • Dashboard guide: https://docs.expo.dev/eas/observe/dashboard/
  • Querying with EAS CLI: https://docs.expo.dev/eas/observe/eas-cli/
  • 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/
  • Third-party integrations: https://docs.expo.dev/eas/observe/integrations/third-party/
  • EAS Update download performance: https://docs.expo.dev/eas/observe/eas-update/
  • Troubleshooting: https://docs.expo.dev/eas/observe/reference/troubleshooting/

Known gaps between the docs and the shipped code

Verified against eas-cli 21.8.0 and expo-observe 57.0.9. Trust this skill's references over the docs on these points, but re-check with --help and the installed package before relying on them:

  • All six CLI commands are on the Querying with EAS CLI page. Older doc builds list only four and omit observe:routes and observe:session.
  • Navigation metric aliases are nav_cold_ttr, nav_warm_ttr, and nav_tti. There are no bare cold_ttr / warm_ttr aliases in the CLI.
  • Sorting uses --sort <slowest|fastest|newest|oldest>. There is no --order flag.
  • ObserveErrorBoundary, Observe.reportError, and configure({ errorHandlingEnabled }) are exported but undocumented. Observe still has no crash reporting; use Sentry or BugSnag for that.

Submitting Feedback

If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:

npx --yes submit-expo-feedback@latest --category skills --subject "eas-observe" "<actionable feedback>"

Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

Related Skills

View on GitHub
GitHub Stars2.6k
CategoryMarketing
Updated1mo ago
Forks153

Languages

Shell

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
eas-observe — Universal Skill: Install & Safety Check | SkillAgent