start-emulator

Launch a specified Android Virtual Device via command line with JSON output.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/powdream/claude-plugins --skill start-emulator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-emulator
Source: https://github.com/powdream/claude-plugins/tree/main/plugins/android-tools/skills/start-emulator
Command: npx skills add https://github.com/powdream/claude-plugins --skill start-emulator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires utils.sh, and includes scripts (resource) components.

What problem does it solve?

This skill automates the process of starting an Android emulator by launching a specific AVD (Android Virtual Device) through a command line interface, removing manual steps and speeding up device readiness for testing and development.

Core Features & Use Cases

  • Launch a specific AVD: Start an Android emulator with quick boot by name, or perform a cold boot if requested.
  • CLI-driven automation: Integrates into CI/CD pipelines to provision test devices on demand.
  • JSON-output for automation: Returns structured JSON indicating success, active AVD, and boot mode, or guidance when multiple emulators exist.

Quick Start

Ensure the Android SDK is installed and ANDROID_HOME or ANDROID_SDK_ROOT is properly set. Then run: bash plugins/android-tools/skills/start-emulator/scripts/start-emulator.sh [avd_name] [boot_type]

Frequently Asked Questions about start-emulator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start an Android emulator from the command line?

You can start an Android emulator from the command line by running the start-emulator script with your target AVD name and boot type. This automates launching the specific Android Virtual Device, removing manual steps and speeding up device readiness for testing.

Can I launch a specific AVD for CI/CD automated testing?

Yes, you can launch a specific AVD for CI/CD automated testing. The skill provides CLI-driven automation to provision test devices on demand and outputs standardized JSON indicating success, active AVD, and boot mode for pipeline integration.

Do I need to set ANDROID_HOME to run an AVD from the CLI?

Yes, you need the Android SDK installed with ANDROID_HOME or ANDROID_SDK_ROOT properly set to run an AVD from the CLI. The skill enforces environment checks for the Android SDK before attempting to boot the emulator.

What is the best way to handle multiple Android emulators in a CI pipeline?

The best way to handle multiple Android emulators in a CI pipeline is using a script that returns structured JSON guidance. This skill outputs standardized JSON indicating available emulators or errors when multiple AVDs exist, streamlining your provisioning workflow.

Does starting an emulator with this script support cold boot?

Yes, starting an emulator with this script supports cold boot if requested. You can pass the desired boot type as an argument to the script to perform either a quick boot or a cold boot of your specific Android Virtual Device.

Why does my Android emulator fail to start in automation scripts?

Your Android emulator might fail to start if the Android SDK is not installed or ANDROID_HOME is not properly set. The skill enforces environment checks for the Android SDK and outputs standardized JSON error results to help diagnose provisioning failures.