From android-tools
Start an Android emulator. Use when you need to launch an AVD for testing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/android-tools:start-emulatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Start an Android emulator (AVD) with quick boot or cold boot option.
Start an Android emulator (AVD) with quick boot or cold boot option.
Script location: scripts/start-emulator.sh (relative to this skill's
directory)
Before running, locate this skill's directory (where this SKILL.md is located), then execute:
bash <skill-directory>/scripts/start-emulator.sh [avd_name] [boot_type]
Arguments:
avd_name (optional): The name of the AVD to startboot_type (optional): "quick" (default) or "cold"{
"success": true,
"message": "Emulator started",
"avd": "Pixel_6_API_33",
"cold_boot": false
}
{
"success": true,
"action": "select_emulator",
"emulators": ["Pixel_6_API_33", "Pixel_4_API_30"]
}
{
"success": false,
"error": "no available emulator",
"hint": "Create an AVD using Android Studio or avdmanager"
}
IMPORTANT: ALWAYS ask the user about boot type before launching. Never skip this step.
Determine emulator:
Ask boot type (REQUIRED - never skip): Use AskUserQuestion to ask
"Quick boot or cold boot?"
Launch: Run script with avd_name and boot_type arguments
Report result: Inform user the emulator is starting or show error
npx claudepluginhub powdream/claude-plugins --plugin android-toolsOrchestrates Android dev tasks — project creation, deployment, SDK management, emulator interaction, and doc search — via the `android` CLI tool.
Automates UI interactions on iOS simulators/devices and Android emulators/devices: open apps, snapshot/screenshot, tap/press, type/fill, scroll, extract UI info. For mobile QA, debugging, replay.
Manages iOS Simulator devices (boot, create, delete) and apps (install, launch) via execute_simulator_command MCP tool for lifecycle, diagnostics, troubleshooting.