AI SummaryControl Android devices via ADB commands to automate interactions like tapping, swiping, typing, and app navigation. Developers building Android automation tools, testing frameworks, or mobile CI/CD pipelines benefit from this skill.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "android-use" skill in my project. Please run this command in my terminal: # Install skill into the correct directory mkdir -p .claude/skills/android-use && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/android-use/SKILL.md "https://raw.githubusercontent.com/shehbajdhillon/android-use/main/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Control Android devices via ADB commands - tap, swipe, type, navigate apps
Prerequisites
• Android device connected via USB with USB debugging enabled • ADB installed and accessible in PATH • Device authorized for debugging (accepted the "Allow USB debugging?" prompt)
Android Device Control Skill
This skill enables you to control Android devices connected via ADB (Android Debug Bridge). You act as both the reasoning and execution engine - reading the device's UI state directly and deciding what actions to take.
Multi-Device Support
All scripts support the -s <serial> flag to target a specific device. This is essential when multiple devices are connected (e.g., a physical phone AND an emulator).
Identifying Devices
Run scripts/check-device.sh to see all connected devices: ` Multiple devices connected (2): [PHYSICAL] 1A051FDF6007PA - Pixel 6 [EMULATOR] emulator-5554 - sdk_gphone64_arm64 Use -s <serial> to specify which device to use. `
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster