Orca Emulator (Android)
FreeControl Android emulators and devices via the Orca CLI.
Free · Opens the source repo
What Orca Emulator (Android) does
The Orca Emulator (Android) skill provides developers with the ability to manage Android emulators and devices directly from the Orca application using the orca command-line interface (CLI). This skill enables a variety of operations such as listing and booting Android Virtual Devices (AVDs), performing touch actions like taps and swipes, simulating typing, and controlling hardware buttons including Back and Recents. Additionally, it supports app installation and launching, managing runtime permissions, and accessing the accessibility tree and logcat for debugging and monitoring purposes. This functionality is designed to streamline the development process for Android applications, making it easier to test and interact with apps in a controlled environment.
The Orca Emulator skill is cross-platform, supporting Windows, Linux, and macOS, which makes it versatile for developers working in different environments. It complements other Orca skills, such as the orca-emulator for iOS and the orca-cli, providing a cohesive toolset for mobile application development. To use the skill effectively, users must ensure they have the correct executable set for their environment, as the skill relies on the orca CLI to function properly. The skill also emphasizes the importance of consulting the full reference guide via the CLI to ensure commands are executed correctly, as command syntax may vary between different versions of the Orca binary.
For developers looking to enhance their workflow with Android emulation, this skill offers a comprehensive set of features that facilitate testing and interaction with Android applications. It is particularly useful for those who need to automate tasks or perform repetitive actions on emulators or connected devices, thereby improving productivity and efficiency in the development lifecycle. By integrating this skill into their development process, users can leverage the power of the Orca CLI to manage their Android testing environments effectively.
When to use it
Use this skill when you need to control Android emulators or devices from within the Orca app, especially for testing and automation.
When not to use it
Avoid this skill if you're not working with Android applications or if you need features specific to iOS emulation, which is covered by a different skill.
What you can build with it
Automating UI Tests
Use the Orca Emulator to automate user interface tests on Android applications, allowing for efficient testing of app functionality.
Debugging Applications
Leverage the logcat feature to debug Android applications in real-time, helping to identify and resolve issues quickly.
Managing Multiple AVDs
Easily manage multiple Android Virtual Devices (AVDs) for testing different configurations and screen sizes.
How to install Orca Emulator (Android)
View source1. Install with the skills CLI
npx skills add stablyai/orca/orca-emulator-android --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by stablyaiOrca Emulator (Android)
This file is a discovery stub, not the usage guide. The full, version-matched Orca Android
emulator reference is served by the orca binary itself — kept out of this file on purpose
so it can never drift from the binary that will actually run your commands.
Engage Orca whenever you drive an adb-connected Android emulator or device from inside the Orca app: listing/booting AVDs, taps, swipes, typing, hardware buttons (including Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat. It is cross-platform (Windows, Linux, macOS) and complements the orca-emulator (iOS) and orca-cli skills.
Resolve the CLI for this session
Choose the executable once and reuse it for every later command:
- If the
ORCA_CLI_COMMANDenvironment 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, useorca-dev. - Otherwise, on Linux outside an Orca-managed terminal, use
orca-ide. Never run bareorcathere — 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 full guide before running Orca commands
ORCA skills get orca-emulator-android
That prints the complete, version-matched guide for the exact binary that will handle your next commands — booting AVDs, taps and swipes, typing, hardware buttons, app lifecycle, permissions, the accessibility tree, and logcat. Read it first, then run the specific command you need.
Don't guess subcommands or flags from memory or from a cached copy of this stub. They
change between Orca releases, and this file deliberately no longer lists them. Confirm the
app is up with ORCA status --json (start it with ORCA open --json if needed), and
prefer --json for agent-driven calls.
If an older Orca does not recognize skills get
Use this fallback only when the selected binary explicitly reports that skills get is an
unknown command. Another failure is not proof of an older binary; report it rather than
guessing or changing executables. For a confirmed pre-guide binary, use only this bounded,
read-only bootstrap to orient. Do not dead-end and do not invent commands:
ORCA status --json
ORCA emulator devices --json
Then tell the user that updating Orca restores the full, version-matched guide via
ORCA skills get orca-emulator-android. Beyond these commands, ask the user rather than
guessing a command surface this older binary may not support.
Frequently asked questions about Orca Emulator (Android)
Similar skills
Android App Development
Comprehensive guide for Android and cross-platform app development.
Add App Clip to Expo App
Integrate lightweight iOS App Clips into your Expo project.
APK Reverse
Streamline your Android APK reverse engineering process.
Swift Expert
Master iOS/macOS development with Swift and SwiftUI.
React Native Expert
Build and optimize mobile apps with React Native and Expo.
Kotlin Specialist
Master idiomatic Kotlin with expert patterns and practices.