mcpField
A
android-cli-ui-automation-skill

android-cli-ui-automation-skill

github.com/takahiromAgent workflows1050 installsUpdated 28w ago
Repository

About android-cli-ui-automation-skill

A skill for agents that automate Android device interfaces through the command line. It pairs an observe-and-act loop with structured layout inspection or screenshots, depending on which is clearer.

Key features

  1. 01Launch apps, URLs, or APKs
  2. 02Inspect structured UI layouts
  3. 03Capture and annotate screenshots
  4. 04Use adb for taps and text input
  5. 05Re-observe after each action

Use cases

  1. 01Automate tasks in app interfaces
  2. 02Handle WebViews, maps, or custom canvases
  3. 03Select a target among connected devices

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/takahirom/android-cli-ui-automation-skill --skill android-cli-ui-automation-skill

After installing, type/android-cli-ui-automation-skillin Claude Code to confirm it loaded.

Bundled filesLICENSEREADME.md

Details

From the project README

Drive the device in a tight launch → observe → act → re-observe loop until the goal is reached. Prefer android layout for structured UI. Use screenshot mode whenever it is faster or more reliable.

If multiple devices are connected, get the serial with adb devices -l. Pass --device=<serial> to android ... and -s <serial> to adb ....

1. Launch

  • URL in a browser: adb -s <serial> shell am start -a android.intent.action.VIEW -d '<url>'
  • Already-installed app: adb -s <serial> shell monkey -p <pkg> -c android.intent.category.LAUNCHER 1
  • APK file: android run --apks=<path> --device=<serial> [--activity=<name>]

2. Observe with android layout

android layout --device=<serial> --pretty --output=/tmp/ui.json

Match targets by text, content-desc, or resource-id. Use the node's center as tap coordinates.

Re-observe after each action with the mode you chose. android layout --device=<serial> --diff is useful when you only need to see what changed.

3. Use screenshot mode when visual targeting is easier

Screenshot mode is often the better choice for:

  • WebView or browser page content
  • Icon-only custom views
  • Canvas, map, or game surfaces
  • Any screen where layout is noisy, incomplete, or slower to interpret than the image
android screen capture --output=/tmp/ui.png --annotate
android screen resolve --screenshot=/tmp/ui.png --string="input tap #N"

Labels are valid only for that screenshot. Capture again after every UI change.

4. Act with adb shell input

adb -s <serial> shell input tap <x> <y>
adb -s <serial> shell input text '<text-with-%s-for-spaces>'
adb -s <serial> shell input swipe <x1> <y1> <x2> <y2> <ms>
adb -s <serial> shell input keyevent <KEYCODE>

Example: adb -s <serial> shell input text 'hello%sworld'

Rules

  • Re-observe after every action. Coordinates and screenshot labels go stale immediately.
  • Clear blockers first: permission dialogs, onboarding sheets, update prompts.
  • Use the observation mode that is clearer: layout for structured UI, screenshot for visual UI.

Notes

  • Don't type URLs into the address bar. Open them with am start -a VIEW -d '<url>'.
  • If the foreground app is unclear, check it with adb -s <serial> shell dumpsys window | rg 'mCurrentFocus|mFocusedApp'.

Comments

Markdown supported