list-devices

Query adb for connected Android devices and emulators, outputting a JSON report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Displaying all connected Android devices and emulators can be tedious when preparing for deployment or debugging. This Skill provides a single, repeatable way to query and verify available targets.

Core Features & Use Cases

  • Device discovery: Enumerates both physical devices and emulators via adb and returns a structured JSON report.
  • Deployment readiness: Lets you confirm which devices are online before an app deployment or a run.
  • Use Case: Before starting a build, run the skill to verify at-a-glance which devices are ready for testing.

Quick Start

Run the script to generate a JSON report of connected devices: bash <skill-directory>/scripts/list-devices.sh

Frequently Asked Questions about list-devices

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

FAQPage Schema
How do I list connected Android devices and emulators for deployment?

List connected Android devices and emulators by querying adb for connected targets. The skill returns a structured JSON report containing serial, type, model, api, and status for each device to verify deployment readiness.

How do I get a JSON report of connected adb targets in a CI pipeline?

Get a JSON report of connected adb targets by running the skill's shell script. It enumerates physical devices and emulators via adb, outputting structured device metadata suitable for automated CI pipeline checks.

Does the Android device discovery script require the adb binary?

Yes, the Android device discovery script requires the adb binary to query connected targets. It relies on adb to extract serial, type, model, api, and status data for each device into a JSON format.

What's the best way to check Android deployment readiness across multiple devices?

Check Android deployment readiness by running the script to generate a JSON report of all connected devices. This provides an at-a-glance view of which physical devices and emulators are online and ready for testing.

Why does the list-devices script output JSON instead of plain text?

The list-devices script outputs JSON instead of plain text to provide structured device data. This format contains serial, type, model, api, and status fields, making it easier to parse in deployment workflows and CI pipelines.

Can I use this skill to verify emulators before a manual device check?

Yes, you can use this skill to verify emulators before a manual device check. It enumerates both physical devices and emulators via adb, returning their status and API levels in a structured JSON report.