Back to Skills

android-device-automation

Vision-driven Android device automation using Midscene. Operates entirely from screenshots — no DOM or accessibility labels required. Can interact with all visible elements on screen regardless of technology stack. Control Android devices with natural language commands via ADB. Perform taps, swipes, text input, app launches, screenshots, and more. Trigger keywords: android, phone, mobile app, tap, swipe, install app, open app on phone, android device, mobile automation, adb, launch app, mobile s

237stars18forksUpdated 6/8/2026

Security Assessment

Medium Risk(50/100)

Detected risks:

Secret Exposure([SKILL.md] API_KEY=)
Sensitive File Access([SKILL.md] .env)
Security Score50/100

About android-device-automation

The Android Device Automation skill enables vision-driven automation of Android devices using the Midscene framework. It eliminates the need for DOM access or accessibility labels, instead relying entirely on screenshots to interpret and interact with on-screen elements. This approach allows for automation across any Android app or interface, regardless of the underlying technology stack, solving the challenge of consistent device testing and interaction in environments where traditional automation methods may fail.

This skill offers a range of capabilities for controlling Android devices via natural language commands executed through ADB. Users can perform taps, double-taps, long-presses, text input, scrolling, swiping in any direction, drag-and-drop, zoom gestures, and system navigation actions like Back, Home, or accessing recent apps. Each action is performed within a single Midscene `act` command, ensuring synchronous execution and accurate screenshot-based feedback. Environment setup includes configuring model-specific API keys and endpoints, supporting models such as Gemini, Qwen 3.5, and Doubao Seed 2.0 Lite.

The skill is ideal for QA engineers, mobile app testers, and developers who need to perform end-to-end testing or visual verification on Android devices. It is particularly useful for testing apps in scenarios where UI elements are dynamic or non-standard, enabling thorough testing and validation without dependency on traditional automation frameworks. Typical use cases include mobile app testing, automation of repetitive tasks on devices, verifying UI functionality, and generating reports based on captured screenshots and performed actions.

FAQ

How do I start using the Android Device Automation skill?

You need to install Midscene for Android using `npx -y @midscene/android@1` and configure the required environment variables for the model you intend to use. Then, you can send natural language commands to control the device.

Which models are compatible with this skill?

Compatible models include Doubao Seed 2.0 Lite, Qwen 3.5, Zhipu GLM-4.6V, Gemini-3-Pro, and Gemini-3-Flash. Ensure you set the appropriate API key, model name, base URL, and model family.

Can I run multiple commands simultaneously?

No, each Midscene command must run synchronously. Running commands in the background or chaining multiple commands together may break the screenshot-analyze-act workflow.

How long does each command take?

Typical commands take around one minute, while complex `act` commands may take longer due to AI inference and screen interaction.

What should I do after completing automation tasks?

Always report task results to the user, including key data found, actions completed, and screenshots taken. Do not end silently after the last automation step.

Install android-device-automation

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill