android-emulator — Claude Code skill: what it does, how to install
This skill drives an Android Emulator with agent-device: it launches apps, checks live UI, and gathers debugging evidence. It fits native, React Native, Expo, and Flutter apps.
npx skills add callstack/agent-device --skill android-emulator -a claude-codeWhat android-emulator does
The skill gives an agent a workflow for operating an app on an Android Emulator. It can open an app or package id, inspect the live UI, tap controls, enter text, and scroll. That supports code-change checks, workflow reproduction, and failure evidence collection.
The agent-device CLI must be installed separately. App launches use an explicit Android target with agent-device open <app-or-package-id> --platform android --foreground. For specialized work, the skill points to help topics for validation, debugging, React Native and Expo, React DevTools, or scripting.
If agent-device is unavailable on PATH, the workflow stops and asks for the CLI to be installed or for an existing installation to be exposed. The skill does not run the CLI installation command by itself.
What it helps with
- launch an app on an Android Emulator
- check live UI after a code change
- reproduce a user workflow
- collect failure evidence
- inspect React Native and Expo with React DevTools
Example prompts for the agent
- Check `<app-or-package-id>` on an Android Emulator: open it with `agent-device open <app-or-package-id> --platform android --foreground`, run the sign-in workflow, and record the failure.
- Launch `<app-or-package-id>` on the Android Emulator, verify the changed screen, tap the relevant controls, enter test data, and collect debugging evidence.
How to install android-emulator
1Skills CLI (Vercel)
npx skills add callstack/agent-device --skill android-emulator -a claude-code2Manually: put the files in place
~/.claude/skills/android-emulator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/android-emulator/
1Skills CLI (Vercel)
npx skills add callstack/agent-device --skill android-emulator -a codex2Manually: put the files in place
.agents/skills/android-emulator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add callstack/agent-device --skill android-emulator -a cursor2Manually: put the files in place
.cursor/skills/android-emulator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install callstack/agent-device android-emulator2Manually: put the files in place
.github/skills/android-emulator/SKILL.md1Skills CLI (Vercel)
npx skills add callstack/agent-device --skill android-emulator -a gemini-cli2Platform CLI
gemini skills install https://github.com/callstack/agent-device --path skills/android-emulatorManually: put the files in place
.devin/skills/android-emulator/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add callstack/agent-device --skill android-emulator -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set4
The whole set →Similar
Questions about android-emulator
How do I install android-emulator in Claude Code?
Run npx skills add callstack/agent-device --skill android-emulator -a claude-code, then run the same command again: npx skills add callstack/agent-device --skill android-emulator -a claude-code. The skill file will be available at ~/.claude/skills/android-emulator/SKILL.md.
What does android-emulator do?
It drives an app on an Android Emulator through agent-device: opening it, inspecting the UI, tapping controls, entering text, scrolling, and gathering evidence for validation or debugging.
What must be installed before using android-emulator?
Install the agent-device CLI separately with npm install -g agent-device@latest. It must be available on PATH, otherwise the skill asks for installation or access to an existing setup.
Source text
SKILL.md · MIT
--- name: android-emulator description: Verify and debug native, React Native, Expo, or Flutter apps on an Android Emulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an Android virtual device. --- # Android Emulator Require the `agent-device` CLI to be installed separately before driving an emulator: ```bash npm install -g agent-device@latest ``` Treat installation and upgrades as user-owned setup steps. Do not run that command autonomously or substitute a mutable `npx -y agent-device@latest` invocation. For a normal app-driving task, start immediately. Do not probe first with `--help`, `--version`, `devices`, `appstate`, `snapshot`, or `screenshot`. Target Android explicitly when opening an app or package id: ```bash agent-device open <app-or-package-id> --platform android --foreground ``` Follow the initial interactive snapshot and corrective error hints. If the shell reports that `agent-device` is unavailable, stop and ask the user to install it or expose their existing installation on `PATH`. Only when the task is specialized or a command shape is unclear, read the relevant version-matched help topic: ```bash agent-device help validate # engineering validation and build freshness agent-device help debugging # screenshots, logs, traces, video, and failures agent-device help react-native # React Native and Expo runtime guidance agent-device help react-devtools # React components, props/state/hooks, render profiling agent-device help scripting # durable replay and CI workflows ```
© callstack · MIT · callstack/agent-device