Name: orca-emulator-android
Author: zpyoung

Imported from zpyoung/orca (skills/orca-emulator-android/SKILL.md). Install upstream with npx skills add zpyoung/orca --skill orca-emulator-android. Copyright stays with the author (Apache-2.0).

Orca Emulator (Android)

This discovery stub loads the version-matched guide from the Orca executable used for this session.

Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

If the ORCA_CLI_COMMAND environment variable is set, use its value. Orca exports this for managed WSL sessions.
Otherwise, in a dev checkout whose session exposes ORCA_DEV_REPO_ROOT, use orca-dev.
Otherwise, on Linux outside an Orca-managed terminal, use orca-ide. Never run bare orca there — outside Orca's terminals it normally resolves to the GNOME Orca screen reader (/usr/bin/orca) and starts speech on the user's machine.
Otherwise, use orca.

Below, ORCA is a placeholder for the executable you resolved. Substitute it before running anything; do not create a shell variable or run ORCA literally. This works the same way in POSIX shells, PowerShell, and cmd.exe.

If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different Orca build.

Load the version-matched guide before running Orca commands

ORCA skills get orca-emulator-android

Prefer --json. Use the selected executable's --help for commands or flags the guide does not cover. If a command reports that Orca is not running, start it with ORCA open --json and retry. If it fails with runtime_access_denied, your sandbox blocked the connection: re-run it with escalated permissions, and do not run ORCA open or restart Orca. If skills get is unknown, explain that updating Orca restores the guide; use --help for read-only discovery and do not guess unsupported commands.

Install orca-emulator-android and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zpyoung-orca-orca-emulator-android", "kind": "skill", "name": "orca-emulator-android", "description": "Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the accessibility tree, and logcat. For an iOS simulator use the iOS emulator skill; build the APK with Gradle first.", "publisher": "zpyoung", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the accessibility tree, and logcat. For an iOS simulator use the iOS emulator skill; build the APK with Gradle first." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zpyoung/orca", "path": "skills/orca-emulator-android/SKILL.md", "ref": "HEAD", "url": "https://github.com/zpyoung/orca/blob/HEAD/skills/orca-emulator-android/SKILL.md", "key": "zpyoung/orca/skills/orca-emulator-android/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# Orca Emulator (Android)\n\nThis discovery stub loads the version-matched guide from the Orca executable used for this session.\n\n## Resolve the CLI for this session\n\nChoose the executable once and reuse it for every later command:\n\n- If the `ORCA_CLI_COMMAND` environment variable is set, use its value. Orca exports this\n for managed WSL sessions.\n- Otherwise, in a dev checkout whose session exposes `ORCA_DEV_REPO_ROOT`, use `orca-dev`.\n- Otherwise, on Linux outside an Orca-managed terminal, use `orca-ide`. Never run bare\n `orca` there — outside Orca's terminals it normally resolves to the\n G", "cost": { "context_tokens": 431 } }

orca-emulator-android

About