android-emulator

Use it when:: You need a native, React Native, Expo or Flutter app checked on an Android virtual device.
It does:: Opens the app on Android with agent-device straight away, follows its interactive snapshot and error hints, and shuts down any emulator it booted when done.
Needs:: The agent-device CLI, which you install yourself; it won't install or upgrade it.
Unlike agent-device:: That one is the repo's general skill for phones, TVs and Macs; this one only targets the Android Emulator and leaves details to agent-device's own help.
For more:: Version-matched agent-device help on validation, debugging, React Native, React DevTools and scripting, read only when a task is specialized.

TL;DR

A short entry point to Callstack's agent-device CLI for Android. The agent skips probing first with --help, devices or a screenshot, opens the app or package id with --platform android in the foreground, then works from the snapshot agent-device returns and its corrective hints. If agent-device isn't on your PATH, it stops and asks you to install it rather than running npx with a moving version. When a task is specialized or a command's shape is unclear, it reads one of agent-device's own help topics: validate for engineering checks and build freshness, debugging for screenshots, logs, traces and video, react-native, react-devtools for components, props, state and render profiling, or scripting for replays and CI. At the end it runs agent-device close --shutdown if it booted the emulator, unless you want it kept running.

Summarizes the skill at 463fd7b.

npx skills add https://github.com/callstack/agent-device --skill android-emulator

skills.sh page Source on GitHub All skills from callstack/agent-device

Total Downloads: 5,500 on skills.sh, Nov 9, 2026
Repo stars: 5,303 callstack/agent-device
First seen: Aug 10, 2026 on skills.sh

Weekly Downloads

451

-1% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	455
Sep 28	542
Oct 5	584
Oct 12	563
Oct 19	460
Oct 26	440
Nov 2	446
Nov 9	451

Category	category:debugging category:computer-use category:software-engineering Find root causes, review code and test what you built. Drive desktop apps, phones and simulators: tap, type, read the screen and test native apps. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills.
Type	type:tool Operates a CLI, API, app or bundled script to get something done.
Effect	effect:local Its own steps create or change files, git state or local tools.
Needs	needs:cli A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI.
Publisher	by:official A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates.
Topics	mobile testing verification computer-use
Stack	stack:agent-device

SKILL.md

From callstack/agent-device at 463fd7b. Checked daily, last changed Nov 7, 2026.

Frontmatter

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:

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:

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.

When you finish, if your session booted the emulator, run agent-device close --shutdown, unless the user asks to keep it running.

Only when the task is specialized or a command shape is unclear, read the relevant version-matched help topic:

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