ADB Connection

Control Android devices via ADB with support for UI layout analysis (uiautomator) and visual feedback (screencap). Use when you need to interact with Android apps, perform UI automation, take screenshots, or run complex ADB command sequences.

Security Scan

This is an instruction-only ADB automation skill that is internally consistent with its stated purpose, but it assumes the presence of the adb tool and will pull files from connected devices — so verify the runtime environment and device trust before use.

Purpose & Capability

The name/description match the instructions: the SKILL.md provides standard ADB, uiautomator, and screencap commands for Android automation. However, the skill metadata lists no required binaries while the instructions clearly require the adb binary (and potentially uiautomator on-device); this mismatch should be corrected or noted by the installer.

Instruction Scope

Instructions stay within the stated scope: connecting via USB/wireless, launching apps, dumping UI hierarchy, input events, and taking screencaps. The SKILL.md does instruct the agent to pull files from the device to the local working directory (e.g., /sdcard/view.xml, /sdcard/screen.png), which is expected for this functionality but is a potential data-exfiltration vector to be aware of.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk or downloaded by the skill itself. This lowers installation risk.

Credentials

The skill requests no environment variables or credentials, which is appropriate. However, it implicitly requires host-level adb access (not declared) and grants access to any connected Android device's filesystem and UI; ensure only trusted devices are connected and that the agent runtime has appropriate permissions.

Persistence & Privilege

always is false and the skill is user-invocable; it does not request persistent presence or modify other skills. The agent may invoke it autonomously (disable-model-invocation is false), which is platform-default — combine that with device access considerations when enabling autonomous runs.

Assessment

This SKILL.md is a straightforward ADB automation recipe and appears coherent, but before installing or using it: 1) confirm the agent runtime has the adb binary on PATH (the skill does not declare this requirement); 2) only connect devices you control or trust — the skill uses adb pull and can copy screenshots and UI dumps from devices to the agent environment; 3) review and approve any commands before allowing autonomous execution (the agent could run adb commands if allowed); 4) if you need tighter controls, require that the skill declare required binaries and document where pulled files are stored, or run the skill in an isolated environment.

Android Automation

Control and automate Android devices using ADB, uiautomator, and screencap.

Connecting Devices

USB Connection

1. Enable Developer Options and USB Debugging on the device.
2. Connect via USB and verify with adb devices.

Wireless Connection (Android 11+)

1. Enable Wireless Debugging in Developer Options.
2. Pairing: Find the IP, port, and pairing code in the "Pair device with pairing code" popup. adb pair <ip>:<pairing_port> <pairing_code>
3. Connecting: Use the IP and port shown on the main Wireless Debugging screen. adb connect <ip>:<connection_port>
4. Verify with adb devices.

Common Workflows

Launching an App

Use the monkey tool to launch apps by package name: adb shell monkey -p <package_name> -c android.intent.category.LAUNCHER 1

Analyzing the UI

Dump and pull the UI hierarchy to find coordinates: adb shell uiautomator dump /sdcard/view.xml && adb pull /sdcard/view.xml ./view.xml

Then grep for text or resource IDs to find bounds="[x1,y1][x2,y2]".

Interacting with Elements

• Tap: adb shell input tap <x> <y>
• Text: adb shell input text "<text>" (Note: Use %\s for spaces in some environments or handle quoting carefully)
• Keyevent: adb shell input keyevent <keycode> (Home: 3, Back: 4, Power: 26, Search: 84, Enter: 66)
• Swipe: adb shell input swipe <x1> <y1> <x2> <y2> <duration_ms>

Visual Verification

Take a screenshot to verify the state: adb shell screencap -p /sdcard/screen.png && adb pull /sdcard/screen.png ./screen.png

Tips

• Search: Use input keyevent 84 to trigger search in many apps.
• Wait: Use sleep <seconds> between commands to allow the UI to update.
• Coordinates: Calculate the center of [x1,y1][x2,y2] for reliable taps.