droid
Skill4 starsChanged 6 months agoMITView on GitHub
This skill should be used when the user asks to "test Android app", "automate Android emulator", "tap button on Android", "take Android screenshot", "interact with Android UI", "ADB automation", "fill Android form", "swipe on emulator", "validate Android UI flow", or needs to control an Android device/emulator via ADB. Provides a unified CLI with JSON output optimized for LLM consumption.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- phuongduyphan/cc-tmux-agentstheir own version, first seen Jun 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- phuongduyphan/cc-tmux-agents★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 76
Wait for element to appear (with timeout).
- Very specific: line 152
Use
--prefer-input: when tapping form fields to avoid hitting labels - Very specific: line 153
Use
--clickable: when tapping buttons to ensure element is interactive - Very specific: line 155
Use
wait-for: instead of blind wait for reliable verification - Very specific: line 159
All errors return JSON with "ok":false:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Droid
Unified Android testing tool with JSON output for LLM-friendly automation.
CLI Discovery
The CLI is located at ./droid-cli/ relative to this SKILL.md file.
| Platform | Script |
| Unix/Linux/macOS | droid |
| Windows | droid.cmd (droid.ps1 also available) |
Prerequisites
- Bun runtime (https://bun.sh)
- ADB (Android Debug Bridge) in PATH
- Connected Android device or running emulator
- USB debugging enabled on device
Quick Start
# Check device connection
droid info
# Screenshot + UI elements (most useful command)
droid screenshot
# Tap by text (no coordinates needed!)
droid tap -t "Book Now"
# Fill a form field in one command
droid fill "Email" "user@example.com"
# Wait for element to appear
droid wait-for -t "Success" -s 5Core Commands
screenshot
Capture screenshot AND UI elements. Returns element coordinates for tapping.
droid screenshot
droid screenshot --clickable # Only clickable elements
droid screenshot --no-ui # Fast, no element dumpResponse: {"ok":true,"screenshot":"/tmp/screenshot.png","elements":[{"text":"Book","class":"Button","clickable":true,"x":540,"y":350,"bounds":[400,300,680,400]}]}
tap
Tap by text or coordinates.
droid tap -t "Book Now" # By text
droid tap -t "State" --prefer-input # Prefer input fields over labels
droid tap -t "Submit" --clickable # Only clickable elements
droid tap 540 960 # By coordinatesfill
Fill text field in one command (tap + clear + type + hide-keyboard).
droid fill "Enter your email" "user@example.com"wait-for
Wait for element to appear (with timeout).
droid wait-for -t "Welcome" -s 10
# Returns: {"ok":true,"found":true,"element":{...}} or {"ok":true,"found":false,"timeout":true}Form Workflow Commands
clear / type / hide-keyboard
droid clear # Clear focused field
droid type "hello@example.com" # Type into focused field
droid hide-keyboard # Dismiss keyboard (use instead of 'key back')key
Send key events.
| Key | Purpose |
back | Navigate back |
enter | Submit/confirm |
move_home | Cursor to start of text |
move_end | Cursor to end of text |
delete | Backspace |
app_home | Android home screen |
droid key back
droid key move_homeOther Commands
| Command | Purpose | Example |
swipe | Scroll | droid swipe up |
longpress | Long press | droid longpress -t "Item" |
launch | Launch app | droid launch com.example.app |
current | Current activity | droid current |
info | Device info | droid info |
wait | Wait ms | droid wait 1000 |
select-all | Select text | droid select-all |
See references/commands.md for full documentation.
Testing Workflow
Recommended Pattern
# 1. Screenshot to see current state
droid screenshot
# 2. Read the screenshot image with Claude's Read tool
# 3. Tap by text when possible
droid tap -t "Book Now" -w 1000
# 4. Verify the action worked
droid wait-for -t "Booking Confirmed" -s 5Form Filling Pattern
# Use fill command for efficiency
droid fill "Email" "user@example.com"
droid fill "Password" "secret123"
droid tap -t "Sign In" --clickable
droid wait-for -t "Welcome" -s 10Tips
- Use
--prefer-inputwhen tapping form fields to avoid hitting labels - Use
--clickablewhen tapping buttons to ensure element is interactive - Use
hide-keyboardnotkey backto dismiss keyboard - Use
wait-forinstead of blindwaitfor reliable verification
Error Handling
All errors return JSON with "ok":false:
droid tap -t "NonexistentButton"
# {"ok":false,"error":"No element found matching 'NonexistentButton'"}Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

