# Android Discovery

> Discover connected Android devices (USB, Wi-Fi, emulator), report serials, states, and capabilities, and confirm uniqueness before a session starts. Use when a device list is needed or a device is not visible.

- Skill: `samraddhashrivastavatech/android-discovery` (Agent Skill)
- Install (CLI): `npx skillmds@latest add samraddhashrivastavatech/android-discovery`
- Raw SKILL.md: https://api.skillmd.com/api/skills/samraddhashrivastavatech/android-discovery/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: SAMRADDHASHRIVASTAVATECH (https://skillmd.com/u/samraddhashrivastavatech)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/samraddhashrivastavatech/android-discovery

---


# Android device discovery

Find every Android device reachable from this host and pin down the exact target
for a session.

## When to use

- Starting any Android session (always the first step).
- A device the user expects is not listed.
- Unplugged / rebooted device needs re-finding.

## Tools used

- `list_devices` — what the ADB server currently knows (serial + state).
- `discover` — actively scan USB / Wi-Fi (adb pair) / emulator transports.
- `status` — detailed state of each candidate.
- `connect` — only after a unique target is agreed.

## Procedure

1. `list_devices` — record the baseline.
2. If the target is missing, `discover` with the appropriate scope (USB, Wi-Fi,
   emulator).
3. If multiple devices appear, stop and ask which serial (or named fleet group)
   to use — never guess.
4. Only after a unique target is confirmed, proceed to `connect` (that is
   `android-adb` territory).

## Security

- Discovery is read-only and safe to run freely.
- The mutative boundary is `connect`: requires human approval.
- Preserve the full list as evidence — a session must know what else is online.

## Related skills

`android-control` · `android-adb` · `android-multi-device`