# Send Midscene Automations Skills for Android to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "midscene-android-automation", "name": "Midscene Automations Skills for Android", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/quanru/midscene-android-automation", "canonicalUrl": "https://clawhub.ai/quanru/midscene-android-automation", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/midscene-android-automation", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=midscene-android-automation", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "midscene-android-automation", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-05T14:32:44.383Z", "expiresAt": "2026-05-12T14:32:44.383Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=midscene-android-automation", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=midscene-android-automation", "contentDisposition": "attachment; filename=\"midscene-android-automation-1.0.2.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "midscene-android-automation" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/midscene-android-automation" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/midscene-android-automation", "downloadUrl": "https://openagent3.xyz/downloads/midscene-android-automation", "agentUrl": "https://openagent3.xyz/skills/midscene-android-automation/agent", "manifestUrl": "https://openagent3.xyz/skills/midscene-android-automation/agent.json", "briefUrl": "https://openagent3.xyz/skills/midscene-android-automation/agent.md" } } ``` ## Documentation ### Android Device Automation CRITICAL RULES — VIOLATIONS WILL BREAK THE WORKFLOW: Never run midscene commands in the background. Each command must run synchronously so you can read its output (especially screenshots) before deciding the next action. Background execution breaks the screenshot-analyze-act loop. Run only one midscene command at a time. Wait for the previous command to finish, read the screenshot, then decide the next action. Never chain multiple commands together. Allow enough time for each command to complete. Midscene commands involve AI inference and screen interaction, which can take longer than typical shell commands. A typical command needs about 1 minute; complex act commands may need even longer. Always report task results before finishing. After completing the automation task, you MUST proactively summarize the results to the user — including key data found, actions completed, screenshots taken, and any relevant findings. Never silently end after the last automation step; the user expects a complete response in a single interaction. Automate Android devices using npx @midscene/android@1. Each CLI command maps directly to an MCP tool — you (the AI agent) act as the brain, deciding which actions to take based on screenshots. ### Prerequisites Midscene requires models with strong visual grounding capabilities. The following environment variables must be configured — either as system environment variables or in a .env file in the current working directory (Midscene loads .env automatically): MIDSCENE_MODEL_API_KEY="your-api-key" MIDSCENE_MODEL_NAME="model-name" MIDSCENE_MODEL_BASE_URL="https://..." MIDSCENE_MODEL_FAMILY="family-identifier" Example: Gemini (Gemini-3-Flash) MIDSCENE_MODEL_API_KEY="your-google-api-key" MIDSCENE_MODEL_NAME="gemini-3-flash" MIDSCENE_MODEL_BASE_URL="https://generativelanguage.googleapis.com/v1beta/openai/" MIDSCENE_MODEL_FAMILY="gemini" Example: Qwen 3.5 MIDSCENE_MODEL_API_KEY="your-aliyun-api-key" MIDSCENE_MODEL_NAME="qwen3.5-plus" MIDSCENE_MODEL_BASE_URL="https://dashscope.aliyuncs.com/compatible-mode/v1" MIDSCENE_MODEL_FAMILY="qwen3.5" MIDSCENE_MODEL_REASONING_ENABLED="false" # If using OpenRouter, set: # MIDSCENE_MODEL_API_KEY="your-openrouter-api-key" # MIDSCENE_MODEL_NAME="qwen/qwen3.5-plus" # MIDSCENE_MODEL_BASE_URL="https://openrouter.ai/api/v1" Example: Doubao Seed 2.0 Lite MIDSCENE_MODEL_API_KEY="your-doubao-api-key" MIDSCENE_MODEL_NAME="doubao-seed-2-0-lite" MIDSCENE_MODEL_BASE_URL="https://ark.cn-beijing.volces.com/api/v3" MIDSCENE_MODEL_FAMILY="doubao-seed" Commonly used models: Doubao Seed 2.0 Lite, Qwen 3.5, Zhipu GLM-4.6V, Gemini-3-Pro, Gemini-3-Flash. If the model is not configured, ask the user to set it up. See Model Configuration for supported providers. ### Connect to Device npx @midscene/android@1 connect npx @midscene/android@1 connect --deviceId emulator-5554 ### Take Screenshot npx @midscene/android@1 take_screenshot After taking a screenshot, read the saved image file to understand the current screen state before deciding the next action. ### Perform Action Use act to interact with the device and get the result. It autonomously handles all UI interactions internally — tapping, typing, scrolling, swiping, waiting, and navigating — so you should give it complex, high-level tasks as a whole rather than breaking them into small steps. Describe what you want to do and the desired effect in natural language: # specific instructions npx @midscene/android@1 act --prompt "type hello world in the search field and press Enter" npx @midscene/android@1 act --prompt "long press the message bubble and tap Delete in the popup menu" # or target-driven instructions npx @midscene/android@1 act --prompt "open Settings and navigate to Wi-Fi settings, tell me the connected network name" ### Disconnect npx @midscene/android@1 disconnect ### Workflow Pattern Since CLI commands are stateless between invocations, follow this pattern: Connect to establish a session Launch the target app and take screenshot to see the current state, make sure the app is launched and visible on the screen. Execute action using act to perform the desired action or target-driven instructions. Disconnect when done Report results — summarize what was accomplished, present key findings and data extracted during the task, and list any generated files (screenshots, logs, etc.) with their paths ### Best Practices Bring the target app to the foreground before using this skill: For best efficiency, launch the app using ADB (e.g., adb shell am start -n ) before invoking any midscene commands. Then take a screenshot to confirm the app is actually in the foreground. Only after visual confirmation should you proceed with UI automation using this skill. ADB commands are significantly faster than using midscene to navigate to and open apps. Be specific about UI elements: Instead of vague descriptions, provide clear, specific details. Say "the Wi-Fi toggle switch on the right side" instead of "the toggle". Describe locations when possible: Help target elements by describing their position (e.g., "the search icon at the top right", "the third item in the list"). Never run in background: Every midscene command must run synchronously — background execution breaks the screenshot-analyze-act loop. Batch related operations into a single act command: When performing consecutive operations within the same app, combine them into one act prompt instead of splitting them into separate commands. For example, "open Settings, tap Wi-Fi, and toggle it on" should be a single act call, not three. This reduces round-trips, avoids unnecessary screenshot-analyze cycles, and is significantly faster. Always report results after completion: After finishing the automation task, you MUST proactively present the results to the user without waiting for them to ask. This includes: (1) the answer to the user's original question or the outcome of the requested task, (2) key data extracted or observed during execution, (3) screenshots and other generated files with their paths, (4) a brief summary of steps taken. Do NOT silently finish after the last automation command — the user expects complete results in a single interaction. Example — Popup menu interaction: npx @midscene/android@1 act --prompt "long press the message bubble and tap Delete in the popup menu" npx @midscene/android@1 take_screenshot Example — Form interaction: npx @midscene/android@1 act --prompt "fill in the username field with 'testuser' and the password field with 'pass123', then tap the Login button" npx @midscene/android@1 take_screenshot ### Troubleshooting ProblemSolutionADB not foundInstall Android SDK Platform Tools: brew install android-platform-tools (macOS) or download from developer.android.com.Device not listedCheck USB connection, ensure USB debugging is enabled in Developer Options, and run adb devices.Device shows "unauthorized"Unlock the device and accept the USB debugging authorization prompt. Then run adb devices again.Device shows "offline"Disconnect and reconnect the USB cable. Run adb kill-server && adb start-server.Command timeoutThe device screen may be off or locked. Wake the device with adb shell input keyevent KEYCODE_WAKEUP and unlock it.API key errorCheck .env file contains MIDSCENE_MODEL_API_KEY=. See Model Configuration.Wrong device targetedIf multiple devices are connected, use --deviceId flag with the connect command. ## Trust - Source: tencent - Verification: Indexed source record - Publisher: quanru - Version: 1.0.2 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-05-05T14:32:44.383Z - Expires at: 2026-05-12T14:32:44.383Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/midscene-android-automation) - [Send to Agent page](https://openagent3.xyz/skills/midscene-android-automation/agent) - [JSON manifest](https://openagent3.xyz/skills/midscene-android-automation/agent.json) - [Markdown brief](https://openagent3.xyz/skills/midscene-android-automation/agent.md) - [Download page](https://openagent3.xyz/downloads/midscene-android-automation)