vybekiit 0.7.33 → 0.7.35

package/dist/global-skills/eas-app-stores/SKILL.md

@@ -171,7 +171,7 @@ Check the CLI version before interpreting a missing command: these submission co
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-app-stores" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-app-stores" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/eas-hosting/SKILL.md

@@ -426,7 +426,7 @@ export async function GET(request: Request) {
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-hosting" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-hosting" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/eas-observe/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: eas-observe
-description: 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
+description: 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`, native crash reporting, source map upload for symbolicated stack traces, 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`, `observe:errors`, `observe:event`), 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.2.1
 license: MIT
 disable-model-invocation: true
 ---
@@ -10,7 +10,7 @@ disable-model-invocation: true
 
 > **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.
+EAS Observe tracks startup, navigation, and custom-event performance from production Expo apps, and records JavaScript errors and native crashes. 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.
 
@@ -19,7 +19,7 @@ EAS Observe tracks startup, navigation, and custom-event performance from produc
 The four reference files in `./references/` cover what people typically need this skill for:
 
 - **Adding EAS Observe to a project** → [`./references/setup.md`](./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`](./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.
+- **Querying metrics from the terminal** → [`./references/queries.md`](./references/queries.md). The `eas observe:*` commands — `metrics-summary`, `metrics`, `routes`, `events`, `session`, `versions`, `errors`, `event` — with flags, metric aliases, table layouts, JSON shapes, and common workflows.
 - **Reading a dashboard or CLI output** → [`./references/metrics.md`](./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`](./references/third-party.md). For package authors only (SDK 57+): optional peer dependency, config declaration merging, `Observe.registerIntegration()`, and event naming.
 
@@ -32,24 +32,16 @@ The four reference files in `./references/` cover what people typically need thi
 - 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/
+- Error reporting: https://docs.expo.dev/eas/observe/errors/
 - 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](https://docs.expo.dev/eas/observe/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:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-observe" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/eas-observe/references/queries.md

@@ -1,6 +1,6 @@
 # EAS Observe CLI
 
-EAS Observe collects app performance telemetry and custom events from Expo apps and exposes them through six EAS CLI commands. Pass the `--help` flag to any command for the latest API — the flags below were verified against `eas-cli` 21.8.0.
+EAS Observe collects app performance telemetry and custom events from Expo apps and exposes them through the `eas observe:*` commands. The CLI changes between releases, so treat `--help` as the source of truth: run `eas observe --help` to list the commands the installed CLI has, and `eas observe:<command> --help` for a command's current flags.
 
 > Source: https://docs.expo.dev/eas/observe/eas-cli/ — the canonical CLI page. This reference adds table layouts, JSON output shapes, and pagination details that the docs page does not cover.
 
@@ -14,18 +14,22 @@ EAS Observe collects app performance telemetry and custom events from Expo apps
 | `eas observe:events` | Custom events emitted by the app via `logEvent` — name summary, all events, or filtered by event name (paginated) |
 | `eas observe:session` | Full timeline of metric and log events for one session |
 | `eas observe:versions` | App version hierarchy with build numbers, OTA update IDs, and event counts |
+| `eas observe:errors` | Error groups by fingerprint; `--fingerprint <id>` lists one group's occurrences with stack traces |
+| `eas observe:event` | One metric, log, or error event by its ID, taken from the `--json` output of `observe:session`, `observe:metrics`, or `observe:events`, or from the occurrences listed by `observe:errors --fingerprint` |
 
-> Older published docs list only `metrics-summary`, `metrics`, `events`, and `versions`. All six are on the [Querying with EAS CLI](https://docs.expo.dev/eas/observe/eas-cli/) page; run `--help` to confirm them on your installed version.
+All commands take these flags:
 
-All six commands share these flags:
-
-- `--start <ISO date>` and `--end <ISO date>` — explicit time range
-- `--days <N>` — show data from the last N days (mutually exclusive with `--start`/`--end`, minimum 1)
 - `--project-id <id>` — run against a specific project without needing a project directory. When passed, the command will not try to create a new EAS project where one is unneeded.
 - `--json` — machine-readable output (implies `--non-interactive`)
 - `--non-interactive` — fail instead of prompting
 
-`--platform ios` / `--platform android` (default: both) is on every command **except `observe:session`**, which is scoped to one session already.
+All commands **except `observe:event`** also take these flags:
+
+- `--start <ISO date>` and `--end <ISO date>` — explicit time range
+- `--days <N>` — show data from the last N days (mutually exclusive with `--start`/`--end`, minimum 1)
+- `--environment <name>` — filter by environment, for example `production` or `development`
+
+`--platform <android|ios|ipados|macos|tvos|apple>` (default: all) is on every command **except `observe:session` and `observe:event`**, which are scoped to one session or one event already. `apple` covers iOS, iPadOS, tvOS, and macOS.
 
 Default time range is the last 60 days when none of `--days`, `--start`, `--end` is given.
 
@@ -86,7 +90,7 @@ eas observe:metrics-summary --metric tti --days 14 --platform ios
 
 **Default stats:** `median` + `eventCount` in the table; all eight in JSON.
 
-This command has no `--limit`, `--after`, `--app-version`, or `--update-id`. It always aggregates every version in the time range.
+This command has no `--limit`, `--after`, `--app-version`, `--build-number`, or `--update-id`. It always aggregates every version in the time range.
 
 **Table layout:**
 - One table per metric (with merged value + event count cells, e.g. `0.45s (150)`)
@@ -141,6 +145,7 @@ eas observe:metrics tti --after <cursor>
 - `--limit <N>` — samples per page (default 10, max 100)
 - `--after <cursor>` — pagination cursor from the previous run
 - `--app-version <version>` — filter by app version string
+- `--build-number <number>` — filter by app build number
 - `--update-id <id>` — filter by EAS update ID
 
 **Table layout:**
@@ -179,7 +184,7 @@ eas observe:routes --after <cursor>
 - `--limit <N>` — routes per page (default **50**, max **200**, different from `metrics`/`events` which default to 10).
 - `--after <cursor>` — pagination cursor from the previous run.
 - `--app-version <version>` — filter by app version string.
-- `--build-number <number>` — filter by app build number (routes-only).
+- `--build-number <number>` — filter by app build number.
 - `--route-name <name>` — filter by route name. Repeatable; only the listed routes are returned across both platforms. Duplicates are de-duplicated; omitting the flag returns all routes.
 - `--update-id <id>` — filter by EAS update ID.
 
@@ -242,6 +247,7 @@ eas observe:events login_failed --after <cursor>
 - `--all-events` — when no event name argument is given, list all events instead of the name summary. Cannot be combined with an event name argument.
 - `--session-id <id>` — filter to events from a single session (events-only). With no event name argument, this lists the session's events instead of the event-name summary. For the full timeline — metrics as well as log events — use `observe:session`.
 - `--app-version <version>` — filter by app version string
+- `--build-number <number>` — filter by app build number
 - `--update-id <id>` — filter by EAS update ID
 - `--limit <N>` — events per page (default 10, max 100)
 - `--after <cursor>` — pagination cursor
@@ -307,7 +313,7 @@ eas observe:session --event-name tti --sort slowest --days 7
 
 **The picker flags and the session ID are mutually exclusive.** `--event-name`, `--sort`, `--days`, `--start`, and `--end` describe how to *find* a session, so passing any of them together with a session ID throws. Query a known session with the ID alone.
 
-This command has no `--platform`, `--limit`, or `--after` flag. It takes the shared time-range, `--project-id`, `--json`, and `--non-interactive` flags.
+This command has no `--platform`, `--limit`, or `--after` flag. It takes the shared time-range, `--environment`, `--project-id`, `--json`, and `--non-interactive` flags.
 
 **JSON output shape:**
 ```json
@@ -322,6 +328,41 @@ This command has no `--platform`, `--limit`, or `--after` flag. It takes the sha
 
 `entries` interleaves metric and log events for the session. The two `hasMore*` flags report truncation per event kind; there is no cursor to page with.
 
+## `eas observe:errors`
+
+Shows error and exception groups, grouped by fingerprint, with event, user, and session counts for each group. The fingerprint is in the first column. Pass `--fingerprint` to list the occurrences of one group, with stack traces, instead of the grouped summary. Error reporting setup is in [`./setup.md`](./setup.md).
+
+```bash
+# Error groups, last 7 days
+eas observe:errors --days 7
+
+# Only fatal errors on Android
+eas observe:errors --severity fatal --platform android
+
+# Occurrences of one group, with stack traces
+eas observe:errors --fingerprint <fingerprint>
+```
+
+**Errors-specific flags:**
+- `--fingerprint <value>` — show the occurrences of this error group instead of the grouped summary
+- `--severity <fatal|error>` — filter by severity (ignored when `--fingerprint` is set)
+- `--app-version <version>`, `--build-number <number>`, `--update-id <id>` — filter by version, build, or EAS update
+- `--limit <N>` — occurrences per page (default 10, max 100). Requires `--fingerprint`.
+- `--after <cursor>` — pagination cursor. Requires `--fingerprint`.
+
+`--limit` or `--after` without `--fingerprint` fails with an error. The grouped summary has no pagination.
+
+## `eas observe:event`
+
+Shows one metric, log, or error event by its ID. Event IDs are in the `--json` output of `observe:metrics`, `observe:events`, and `observe:session`, and in the occurrences from `observe:errors --fingerprint`.
+
+```bash
+eas observe:event <event-id>
+eas observe:event <event-id> --json
+```
+
+`ID` is a required positional argument. The command takes only `--project-id`, `--json`, and `--non-interactive`.
+
 ## `eas observe:versions`
 
 Shows app version hierarchy with build numbers, OTA update IDs, and event counts per version.

package/dist/global-skills/eas-observe/references/setup.md

@@ -403,15 +403,17 @@ User-defined events are persisted on-device, batched, and dispatched on the next
 
 User-defined events appear under the **Events** tab in the Observe dashboard, and are queryable from the terminal with `eas observe:events` — see [`./queries.md`](./queries.md).
 
-## Optional — error reporting
+## Optional — error and crash reporting
 
-`expo-observe` records errors as non-fatal `exception` log events alongside the performance metrics. They arrive by three paths, and they are **not** a replacement for a crash reporter such as Sentry — EAS Observe has no crash reporting yet.
+`expo-observe` records JavaScript errors and native crashes alongside the performance metrics. Errors are persisted on-device, batched, and dispatched on the next flush. They appear on the **Observe > Errors** page of the dashboard. Docs: https://docs.expo.dev/eas/observe/errors/
 
-> These APIs ship in `expo-observe` but are not covered by the published docs yet. Verify the exports against the installed package version before relying on them.
+> Error reporting is in **preview** and requires SDK 57+. Native crashes additionally require `expo-observe` 57.0.21+.
 
-**1. Unhandled JS errors — automatic.** A global `ErrorUtils` handler is installed when the package is first imported, which is earlier than any `configure()` call, so errors thrown before configuration are still recorded. React Native's own behavior is unchanged: the red box in development and fatal termination in production still happen. Turn the recording off with `configure({ errorHandlingEnabled: false })`.
+JavaScript errors arrive by three paths.
 
-**2. Render-phase errors — `<ObserveErrorBoundary>`.** Render errors never reach `ErrorUtils`, so a boundary is the only way to capture them with the React component stack. The boundary records the error and then renders `fallback` in place of the subtree.
+**1. Unhandled JS errors — automatic.** A global `ErrorUtils` handler is installed when the package is first imported, which is earlier than any `configure()` call, so errors thrown before configuration are still recorded. React Native's own behavior is unchanged: the red box in development and fatal termination in production still happen. Turn the recording off with `configure({ errorHandlingEnabled: false })`. This only affects unhandled JS errors — boundary errors, `reportError` calls, and native crashes are still recorded.
+
+**2. Render-phase errors — `<ObserveErrorBoundary>`.** Without a boundary, a render error is recorded by the global handler as an unhandled error. A boundary records it with the React component stack and then renders `fallback` in place of the subtree.
 
 ```tsx
 import { ObserveErrorBoundary } from 'expo-observe';
@@ -424,6 +426,22 @@ import { ObserveErrorBoundary } from 'expo-observe';
 
 `fallback` is required and accepts a React element, `null`, or a function receiving `{ error, resetError }`. `resetError()` clears the caught error and re-mounts the children, so they restart from a clean state. There is no capture-and-rethrow mode — a boundary always renders one of the three fallback forms. Errors that no boundary catches still reach the global handler.
 
+For an app-wide boundary, pass `errorBoundaryFallback` to `ObserveRoot`. `ObserveRoot.wrap(Component)` takes no options, so replace `export default ObserveRoot.wrap(RootLayout)` with an outer wrapper that keeps `RootLayout` beneath `ObserveRoot`:
+
+```tsx
+export default function ObservedRootLayout() {
+  return (
+    <ObserveRoot errorBoundaryFallback={<FallbackScreen />}>
+      <RootLayout />
+    </ObserveRoot>
+  );
+}
+```
+
+Keep your existing `RootLayout` beneath `ObserveRoot` when making this change. Rendering `<ObserveRoot>` inside a layout is fine only when that layout just returns the wrapper and its children.
+
+`ObserveRoot.wrap(RootLayout)` stays correct when no custom boundary is needed. Without `errorBoundaryFallback`, no root boundary is mounted and render errors are recorded by the global handler without the component stack. Pass `errorBoundaryFallback={null}` to capture render errors and render nothing after an error.
+
 **3. Handled errors — `Observe.reportError(error)`.** Report failures your code caught and recovered from, which reach neither the global handler nor a boundary.
 
 ```tsx
@@ -434,7 +452,42 @@ try {
 }
 ```
 
-The value is normalized before it is sent: an `Error` contributes `name`, `message`, and `stack`; any other thrown value (a string, a plain object, a number) is stringified into the message with no stack. `reportError` never throws — it is called from a `catch` block, so a failure inside it must not turn a handled error into an unhandled one.
+The value is normalized before it is sent: an `Error` contributes `name`, `message`, and `stack`; any other thrown value (a string, a plain object, a number) is stringified into the message with no stack. `reportError` never throws — it is called from a `catch` block, so a failure inside it must not turn a handled error into an unhandled one. Keep PII out of error messages; everything reported leaves the device and is visible in the dashboard.
+
+### Native crashes — automatic
+
+With `expo-observe` 57.0.21+, native crashes are recorded with no setup. The report is written on the device and dispatched on the **next launch**, so a recent crash can take time to appear. They show with the **Native** source in the dashboard.
+
+- **Android:** uncaught Java/Kotlin exceptions, including the `Caused by` chain. On Android 11+, also the OS crash records for native-code crashes such as `SIGSEGV` and `SIGABRT`.
+- **iOS:** MetricKit crash reports — Mach exceptions (`EXC_BAD_ACCESS`, `EXC_BREAKPOINT`) and Unix signals (`SIGSEGV`, `SIGBUS`, `SIGTRAP`). On iOS 17+, also uncaught Objective-C and Swift exceptions.
+- **Not recorded:** tvOS, the iOS Simulator, ANRs, and out-of-memory terminations.
+
+### Symbolicated stack traces
+
+Production JS stack traces point into the minified bundle unless a source map is stored for the code that threw. Errors from the embedded bundle use the **build's** source map; errors from an OTA bundle use the **update's** source map. Upload both.
+
+**Builds** — set `uploadSourceMaps` in the build profile:
+
+```json
+{ "build": { "production": { "uploadSourceMaps": true } } }
+```
+
+- Requires EAS CLI 22.0.0+ and a build on EAS Build servers. `eas build --local` does not upload source maps.
+- `sourcesContent` is stripped before upload; only file names and mappings are stored. A failed upload only warns — the build still completes.
+
+**EAS Updates** — publish with `--upload-source-maps` (EAS CLI 24.9.0+):
+
+```bash
+eas update --channel production --upload-source-maps
+```
+
+- Uploads the map `expo export` emits for each native platform, with `sourcesContent` stripped.
+- Maps over the 5 MiB upload limit are skipped with a warning; publishing never fails because of a source map.
+- The error detail page links the update that supplied the map next to **Stack trace**, as it does for the build.
+
+**Not available yet:** native symbolication (no dSYM or ProGuard mapping upload). Native frames show symbol names on iOS and class/method/line on Android.
+
+If the user needs ANR/OOM capture or native symbolication today, a separate crash reporter such as Sentry is still the option for that gap.
 
 ## Optional — runtime configuration
 
@@ -472,5 +525,5 @@ The URL is baked into the native layer at build time, so run `npx expo prebuild`
 - [ ] (Optional, SDK 56+) Per-route metrics enabled via `Observe.configure({ integrations: { ... } })`, plus `<ObserveNavigationContainer>` (dynamic) or `<ObserveNavigationProvider>` (static) for React Navigation.
 - [ ] (Optional, SDK 57+) Sensitive route/query params listed in `filteredParams`.
 - [ ] (Optional, SDK 56+) User-defined events emitted via `Observe.logEvent(name, { attributes })` with stable, lowercase, dot-separated names and no PII.
-- [ ] (Optional) `<ObserveErrorBoundary>` around risky subtrees and `Observe.reportError` in recovery paths.
+- [ ] (Optional, SDK 57+) `<ObserveErrorBoundary>` (or `errorBoundaryFallback` on `ObserveRoot`) around risky subtrees, `Observe.reportError` in recovery paths, `"uploadSourceMaps": true` in the `eas.json` build profile, and `eas update --upload-source-maps` when publishing updates.
 - [ ] New build produced with `eas build` and metrics visible in the Observe dashboard.

package/dist/global-skills/eas-simulator/SKILL.md

@@ -232,7 +232,7 @@ Source of truth: Expo docs and the `eas` / `agent-device` CLIs (`npx --yes eas-c
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-simulator" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-simulator" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/eas-simulator/references/run-your-app.md

@@ -219,6 +219,8 @@ The launch-args are iOS UserDefaults (`-Key Value`), verified in expo/expo `pack
 
 Method 1 passes each as two flags: `--launch-arg "<key>" --launch-arg "<value>"`. Method 2 passes them as `--launch-args`.
 
+On SDK 58+, you can put the same switches in the URL instead, which also works on **Android**, where launch-args don't apply: append `__expo_disable_onboarding=1&__expo_disable_fab=1&__expo_disable_auto_launch=1` to the `exp://` URL or to `<scheme>://?__expo_url=<encoded manifest URL>`. On SDK 57 and earlier, keep the launch-args on iOS; on Android, the legacy dev client URL takes `&disableOnboarding=1&disableFab=1&disableAutoLaunch=1` after `url=` (`disableFab` and `disableAutoLaunch` need `expo-dev-launcher` 57.0.20+). See `../../expo-overview/references/launch-without-dev-menu.md`.
+
 ### Metro tunnel backends (both methods)
 
 #### Tunnel scope and approvals

package/dist/global-skills/eas-update/SKILL.md

@@ -141,7 +141,7 @@ Never bypass a compatibility or anti-bricking safeguard merely to make an update
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-update" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-update" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/eas-update-insights/SKILL.md

@@ -233,7 +233,7 @@ Human-readable group details plus 30 days of launches/failures per platform —
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-update-insights" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-update-insights" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/eas-workflows/SKILL.md

@@ -94,7 +94,7 @@ When users ask about available options (job types, triggers, runner types, etc.)
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "eas-workflows" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "eas-workflows" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-animation/SKILL.md

@@ -269,7 +269,7 @@ Opinionated and brief. When the honest answer is "this shouldn't animate," or "t
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-animation" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-animation" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-app-clip/SKILL.md

@@ -285,7 +285,7 @@ See [./references/native-module.md](./references/native-module.md) for the Swift
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-app-clip" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-app-clip" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-brownfield/SKILL.md

@@ -64,7 +64,7 @@ Open the RN screen with input, return a result to native, dismiss, and reopen wi
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-brownfield" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-brownfield" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-data-fetching/SKILL.md

@@ -473,7 +473,7 @@ User: "How do I load data for a page in Expo Router?"
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-data-fetching" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-data-fetching" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-design-system/SKILL.md

@@ -371,7 +371,7 @@ To measure drift in an app that already has screens - hardcoded hex values, arbi
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-design-system" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-design-system" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-dev-client/SKILL.md

@@ -153,6 +153,8 @@ npx expo start --dev-client
 # Scan QR code with dev client or enter URL manually
 ```
 
+When you launch the dev client yourself to screenshot or drive it, skip the onboarding sheet, the dev menu at launch, and the Tools button. On SDK 58+, Expo CLI does this for launches it starts from a non-interactive shell; for a URL you open yourself, use `<scheme>://?__expo_url=<encoded dev server URL>&__expo_disable_onboarding=1&__expo_disable_fab=1&__expo_disable_auto_launch=1`. On SDK 57 and earlier, launch the iOS app with the `-EXDevMenu*` launch arguments, and on Android open `<scheme>://expo-development-client/?url=<encoded dev server URL>&disableOnboarding=1&disableFab=1&disableAutoLaunch=1`. See `../expo-overview/references/launch-without-dev-menu.md` for the exact commands.
+
 ## Troubleshooting
 
 **Build fails with signing errors:**
@@ -177,7 +179,7 @@ eas update
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-dev-client" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-dev-client" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-dom/SKILL.md

@@ -420,7 +420,7 @@ On web, the `dom` prop is ignored since no webview is needed.
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-dom" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-dom" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-examples/SKILL.md

@@ -101,7 +101,7 @@ When the user already has an app, **add only what the example introduces; never
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-examples" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-examples" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-migrate-module/SKILL.md

@@ -119,7 +119,7 @@ Report:
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-migrate-module" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-migrate-module" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-module/SKILL.md

@@ -146,7 +146,7 @@ Note: iOS uses just the class name; Android uses the fully-qualified class name
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-module" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-module" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-native-ui/SKILL.md

@@ -196,7 +196,7 @@ Use CSS `boxShadow` style prop. NEVER use legacy React Native shadow or elevatio
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-native-ui" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-native-ui" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-overview/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: expo-overview
 description: "Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules."
-version: 1.1.0
+version: 1.2.0
 license: MIT
 disable-model-invocation: true
 ---
@@ -58,7 +58,6 @@ Match the goal to a category, then the skill, then load that leaf's `SKILL.md`.
 **Maintain & learn**
 - `expo-upgrade` — upgrade the Expo SDK and fix dependency conflicts
 - `expo-examples` — canonical, version-matched integration examples (Stripe, Clerk, Supabase, …)
-- `expo-skill-feedback` — send feedback on an Expo skill or on Expo itself; enable / disable the anonymous usage telemetry
 
 ### Translating vague asks
 
@@ -95,6 +94,12 @@ Apply the rules that match the project and the requested task.
   native-setup steps differ — note which one the project is in.
 - **Install packages with `npx expo install <pkg>`**, not raw `npm`/`yarn`/`pnpm add`,
   so versions stay compatible with the project's SDK.
+- **Launching the app yourself?** When you open Expo Go or a development build to look
+  at, screenshot, or drive it, skip the first-launch onboarding, the dev menu that opens
+  at launch, and the floating Tools button. On SDK 58+, Expo CLI does this for launches
+  it starts from a non-interactive shell. On SDK 57 and earlier, and for any URL you open
+  yourself (`simctl openurl`, `adb`, a controller), follow
+  `./references/launch-without-dev-menu.md`.
 - **EAS auth & linking** (only needed for build/submit/update/observe/workflows): check
   login with `eas whoami`, log in with `eas login`. A project is linked when
   `extra.eas.projectId` exists in the app config; create it with `eas init` if missing.
@@ -110,7 +115,7 @@ Apply the rules that match the project and the requested task.
 ## Submitting Feedback
 If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
 ```bash
-npx --yes submit-expo-feedback@latest --category skills --subject "expo-overview" "<actionable feedback>"
+npx --yes @expo/agent-cli@latest feedback --category skills --subject "expo-overview" "<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.
+If an agent repeatedly fails at an Expo task or the user has to step in, submit a brief report of the task, expected result, and what went wrong using `--category evals` and the relevant Expo package or command as `--subject`.

package/dist/global-skills/expo-overview/references/launch-without-dev-menu.md

@@ -0,0 +1,24 @@
+# Launch without onboarding or the dev menu
+
+When you launch Expo Go or a development build yourself, suppress the onboarding sheet, the dev menu at launch, and the Tools button with launch flags. Don't change app config for this.
+
+**SDK 58+:** Expo CLI adds the flags itself when it has no TTY (force with `EXPO_NO_DEV_MENU=1`). For URLs you open yourself, append `__expo_disable_onboarding=1&__expo_disable_fab=1&__expo_disable_auto_launch=1` to `exp://<host>:8081` or `<scheme>://?__expo_url=<encoded dev server URL>`.
+
+**SDK 57 and earlier, iOS:** launch with these arguments before opening the URL. They last for that process only.
+
+```bash
+xcrun simctl launch --terminate-running-process booted <bundle id> \
+  -EXDevMenuIsOnboardingFinished 1 -EXDevMenuShowsAtLaunch 0 -EXDevMenuShowFloatingActionButton 0
+```
+
+**SDK 57 and earlier, Android:** append `&disableOnboarding=1&disableFab=1&disableAutoLaunch=1` to `<scheme>://expo-development-client/?url=<encoded dev server URL>`. Only `disableOnboarding` works before `expo-dev-launcher` 57.0.20. Expo Go has no flag, so dismiss its onboarding once.
+
+**Opening URLs:** on Android, use `adb shell "am start -a android.intent.action.VIEW -d '<url>'"`. The inner quotes keep the URL's `&`. On iOS, `simctl openurl` shows an "Open in '<app>'?" prompt for any scheme not yet approved. Approve it first:
+
+```bash
+P=~/Library/Developer/CoreSimulator/Devices/<udid>/data/Library/Preferences/com.apple.launchservices.schemeapproval.plist
+K="com.apple.CoreSimulator.CoreSimulatorBridge--><scheme>"
+/usr/libexec/PlistBuddy -c "Set :'$K' <bundle id>" "$P" 2>/dev/null || /usr/libexec/PlistBuddy -c "Add :'$K' string <bundle id>" "$P"
+```
+
+Expo Go's bundle id is `host.exp.Exponent`, and its scheme is `exp`.