Android CLI tools: adb, emulator control, and device management

Install

/plugin install android-tools@powdream-plugins

Run it inside Claude Code after adding the marketplace with /plugin marketplace add powdream/claude-plugins.

Contents

Discovered from source

Skills 6

Connect Device

Connect to an Android device over ADB wireless (TCP/IP).

Instructions

Script location: scripts/connect-device.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/connect-device.sh [ip:port]
# or
bash <skill-directory>/scripts/connect-device.sh [ip] [port]

Arguments:

  • ip:port: IP address and port in format "192.168.1.100:5555"
  • Or separate arguments: ip and port (default port: 5555)

JSON Output Schema

Success

{
  "success": true,
  "message": "Connected to 192.168.1.100:5555",
  "ip": "192.168.1.100",
  "port": "5555"
}

Request Input (no arguments)

{
  "success": true,
  "action": "request_input",
  "message": "Please provide IP address and port"
}

Failure

{
  "success": false,
  "error": "Failed to connect to 192.168.1.100:5555",
  "hint": "Ensure the device is on the same network and ADB over WiFi is enabled"
}

Claude's Handling

  1. If JSON has action: "request_input", use AskUserQuestion to ask for IP and port
  2. Report connection result to user

Disconnect Device

Disconnect a wireless Android device from ADB.

Instructions

Script location: scripts/disconnect-device.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/disconnect-device.sh [argument]

Arguments:

  • all: Disconnect all wireless devices
  • ip:port (e.g., 192.168.1.100:5555): Disconnect specific device
  • (none): Auto-detect wireless devices

JSON Output Schema

Success - Single Device

{
  "success": true,
  "message": "Disconnected from 192.168.1.100:5555",
  "serial": "192.168.1.100:5555"
}

Success - All Devices

{
  "success": true,
  "message": "Disconnected all wireless devices"
}

No Wireless Devices

{
  "success": true,
  "message": "No wireless devices connected"
}

Select Device (multiple wireless devices)

{
  "success": true,
  "action": "select_device",
  "devices": [
    { "serial": "192.168.1.100:5555", "model": "Pixel 6", "api": "33" },
    { "serial": "192.168.1.101:5555", "model": "Galaxy S21", "api": "31" }
  ]
}

Failure

{
  "success": false,
  "error": "adb not found",
  "hint": "Set ANDROID_HOME or ANDROID_SDK_ROOT environment variable"
}

Claude's Handling

  1. If JSON has action: "select_device", use AskUserQuestion to let user choose:
    • "all" - Disconnect all wireless devices
    • Individual devices (show model and API info)
  2. After user selection, run the script again with the selected argument
  3. Report disconnect result to user
  4. On failure, show the error message and hint to the user

List Devices

Display connected Android devices and emulators using adb.

Instructions

Script location: scripts/list-devices.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/list-devices.sh

The script outputs JSON with device details.

JSON Output Schema

Success

{
  "success": true,
  "count": 2,
  "devices": [
    {
      "serial": "emulator-5554",
      "type": "emulator",
      "model": "sdk_gphone64_arm64",
      "api": "33",
      "status": "device"
    },
    {
      "serial": "RF8M33XXXXX",
      "type": "physical",
      "model": "SM-G998N",
      "api": "31",
      "status": "device"
    }
  ]
}

Failure

{
  "success": false,
  "error": "adb not found",
  "hint": "Set ANDROID_HOME or ANDROID_SDK_ROOT environment variable",
  "devices": []
}

Formatting the Output

Success (success: true)

Format the JSON output as a table:

Connected Devices (2):

  SERIAL            TYPE       MODEL              API    STATUS
  --------------------------------------------------------------
  emulator-5554     emulator   sdk_gphone64_arm64 33     device
  RF8M33XXXXX       physical   SM-G998N           31     device
  • Show empty fields as "-"
  • If count is 0, show "No devices connected."

Failure (success: false)

Show the error message and hint to the user:

Error: adb not found
Hint: Set ANDROID_HOME or ANDROID_SDK_ROOT environment variable

List Emulators

Display installed Android emulators (AVDs) with detailed information.

Instructions

Script location: scripts/list-emulators.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/list-emulators.sh

The script outputs JSON with emulator details.

JSON Output Schema

Success

{
  "success": true,
  "count": 2,
  "emulators": [
    {
      "name": "Pixel_6_API_33",
      "device": "pixel_6",
      "api": "33",
      "resolution": "1080x2400",
      "image": "google_apis_playstore",
      "playstore": true
    }
  ]
}

Failure

{
  "success": false,
  "error": "emulator not found",
  "hint": "Set ANDROID_HOME or ANDROID_SDK_ROOT environment variable",
  "emulators": []
}

Formatting the Output

Success (success: true)

Format the JSON output as a table:

Installed Emulators (2):

  NAME                DEVICE      API    RESOLUTION   IMAGE                  PLAYSTORE
  ------------------------------------------------------------------------------------
  Pixel_6_API_33      pixel_6     33     1080x2400    google_apis_playstore  Yes
  Pixel_4_API_30      pixel_4     30     1080x2280    google_apis            No
  • Display playstore: true as "Yes", false as "No"
  • Show empty fields as "-"

Failure (success: false)

Show the error message and hint to the user:

Error: emulator not found
Hint: Set ANDROID_HOME or ANDROID_SDK_ROOT environment variable

Start Emulator

Start an Android emulator (AVD) with quick boot or cold boot option.

Instructions

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 start
  • boot_type (optional): "quick" (default) or "cold"

JSON Output Schema

Success - Launch

{
  "success": true,
  "message": "Emulator started",
  "avd": "Pixel_6_API_33",
  "cold_boot": false
}

Success - Multiple emulators (ask user)

{
  "success": true,
  "action": "select_emulator",
  "emulators": ["Pixel_6_API_33", "Pixel_4_API_30"]
}

Failure

{
  "success": false,
  "error": "no available emulator",
  "hint": "Create an AVD using Android Studio or avdmanager"
}

Claude's Handling

IMPORTANT: ALWAYS ask the user about boot type before launching. Never skip this step.

Flow

  1. Determine emulator:

    • If user specified an emulator name → use that name
    • Otherwise → run script with no arguments to get the list, then ask user to select if multiple emulators exist
  2. Ask boot type (REQUIRED - never skip): Use AskUserQuestion to ask "Quick boot or cold boot?"

    • First option: "Quick boot (Recommended)"
    • Second option: "Cold boot"
  3. Launch: Run script with avd_name and boot_type arguments

  4. Report result: Inform user the emulator is starting or show error

Stop Emulator

Stop a running Android emulator (AVD).

Instructions

Script location: scripts/stop-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/stop-emulator.sh [avd_name_or_serial]

Arguments:

  • avd_name_or_serial (optional): The name of the AVD (e.g., Pixel_6_API_33) or serial (e.g., emulator-5554) to stop

JSON Output Schema

Success

{
  "success": true,
  "message": "Emulator stopped",
  "avd": "Pixel_6_API_33",
  "serial": "emulator-5554"
}

Success - Multiple running (ask user)

{
  "success": true,
  "action": "select_emulator",
  "running": [
    { "avd": "Pixel_6_API_33", "serial": "emulator-5554" },
    { "avd": "Pixel_4_API_30", "serial": "emulator-5556" }
  ]
}

Failure

{
  "success": false,
  "error": "no running emulator",
  "hint": "Start an emulator first using start-emulator skill"
}

Claude's Handling

  1. If JSON has action: "select_emulator", use AskUserQuestion to let user choose which emulator to stop
  2. After successful stop, inform user the emulator has been stopped
  3. On failure, show the error message and hint to the user

Sponsors

Details

Marketplace
powdream/claude-plugins
Source
plugins/android-tools
Category
Community

More from powdream/claude-plugins

All 8