| name | android-test |
| trigger | /android-test |
| description | Test an Android app on a leased worker emulator or physical device using mobile-mcp and adb evidence |
| parameters | [{"name":"app","required":false},{"name":"flow","required":true},{"name":"device","required":false}] |
Android Test Skill
Use when the user asks to install, launch, inspect, screenshot, or test an Android app.
Workflow
- Confirm the Android device lease section in the prompt and copy the exact serial.
- Use mobile-mcp tools with that serial as the
device parameter on every call.
- If an APK path is provided, install it on the leased serial only.
- Launch the app and capture a starting screenshot.
- Execute the requested flow with mobile-mcp. Use adb only for evidence or diagnostics that mobile-mcp cannot provide.
- Return a concise report with device serial, app/package, steps run, screenshots/log snippets, pass/fail, and blockers.
Rules
- Do not touch Android serials other than the leased serial.
- Prefer accessibility tree selectors over coordinate taps when available.
- Capture screenshots before and after risky navigation.
- If the device is offline, unauthorized, or missing, stop and report the state instead of retrying unrelated serials.