From android-tools
List connected Android devices and emulators. Use when you need to check available devices for deployment or debugging.
How this skill is triggered — by the user, by Claude, or both
Slash command
/android-tools:list-devicesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Display connected Android devices and emulators using adb.
Display connected Android devices and emulators using adb.
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.
{
"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"
}
]
}
{
"success": false,
"error": "adb not found",
"hint": "Set ANDROID_HOME or ANDROID_SDK_ROOT environment variable",
"devices": []
}
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
count is 0, show "No devices connected."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
npx claudepluginhub powdream/claude-plugins --plugin android-toolsUse when working with Android devices via ADB - connecting devices, running shell commands, installing apps, debugging, taking screenshots, UI automation, viewing logs, analyzing crashes, or exploring system internals. Triggers on "adb", "logcat", "install apk", "debug android", "android device", "shell command", "screenshot", "dumpsys", "crash", "ANR".
Orchestrates Android dev tasks — project creation, deployment, SDK management, emulator interaction, and doc search — via the `android` CLI tool.
Drives Kobiton mobile devices interactively from natural language. Translates intents into WebDriver actions, ADB commands, file transfers, and app management via the Kobiton CLI.