Android Emulator

by callstack5ee37f30a8dfNo license4.9K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

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.

Instructions onlySoftware Development

AI-generated overview

Drives an Android emulator via the agent-device CLI to launch apps, inspect live UI, and validate changes.

What it does: This skill provides instructions for using the agent-device CLI to operate an Android Emulator. It covers opening an app or package id with an explicit Android platform target, then following interactive snapshots and error hints to tap, type, scroll, and inspect the live UI. It also points to version-matched help topics for validation, debugging, React Native/Expo, React DevTools, and scripting workflows.
When to use it: Use it when an agent needs to launch a native, React Native, Expo, or Flutter app on an Android virtual device. It fits tasks such as validating a code change, collecting failure evidence, or reproducing a workflow on an emulator.
Requirements: Requires the agent-device CLI installed separately, typically via a global npm install that the user performs; the skill ships no scripts and only contains instructions. A running Android Emulator and shell access to the CLI on PATH are needed.

Android Emulator

Require the agent-device CLI to be installed separately before driving an emulator:

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:

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 freshnessagent-device help debugging       # screenshots, logs, traces, video, and failuresagent-device help react-native    # React Native and Expo runtime guidanceagent-device help react-devtools  # component tree, props/state/hooks, and rendersagent-device help scripting       # durable replay and CI workflows

agent-device help validate        # engineering validation and build freshnessagent-device help debugging       # screenshots, logs, traces, video, and failuresagent-device help react-native    # React Native and Expo runtime guidanceagent-device help react-devtools  # component tree, props/state/hooks, and rendersagent-device help scripting       # durable replay and CI workflows

Source and attribution

Source:callstack/agent-deviceinskills/android-emulatorat commit5ee37f3

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Android Emulator

Android Emulator

Source and attribution

More from callstack/agent-device

Ios Simulator

Agent Device

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices