phone-harness
GitHub通过ADB工具控制物理Android手机,执行应用操作、屏幕交互及自动化测试。适用于明确的安卓设备操控、UI测试及移动端自动化场景。
Trigger Scenarios
Install
npx skills add milind-soni/OpenMausBot --skill phone-harness -g -y
SKILL.md
Frontmatter
{
"name": "phone-harness",
"description": "Control, inspect, test, or automate a physical Android phone connected to OpenMausBot over authorized USB debugging. Use for explicit Android, USB phone, ADB, mobile-app, tapping, typing, swiping, scrolling, screenshot, or phone-screen requests."
}
Phone Harness
Use the phone tools for every requested Android action. Never replace them
with Bash, raw adb, subprocess, an emulator, network ADB, or Tailscale.
- Call
statusbefore the first action. If the device is missing or unauthorized, stop and relay the physical setup instruction. - Call
open_appwith the human app name. Do not scan the launcher first. Uselist_appsonly when the name is ambiguous. - Call
read_screenbefore choosing a target and after every action. Prefertap_text; usescreenshotand pixeltaponly when accessibility text cannot identify the target. - Use
swipe,type_text, andpressfor interaction, verifying each step.
The tools operate the user's real phone. Navigate and read only what the task needs. Stop before sending, posting, purchasing, booking, deleting, changing settings, entering protected information, or accepting an unexpected legal or security prompt unless the user has explicitly authorized that exact action.
Never enter passwords, payment details, government identifiers, or one-time codes. Ask the user to complete protected-input steps directly on the phone.
Version History
- 4ea27e7 Current 2026-08-19 11:43


