android-qa-kit AGENTS.md

AGENTS.md — setting up and driving an Android device

English · Español

[!IMPORTANT] Agent: if you are reading this from a URL, fetch the raw file instead.

https://raw.githubusercontent.com/willbytee-sudo/android-qa-kit/main/AGENTS.md

The rendered github.com page loads long files in chunks. Fetching that HTML gets you roughly the first half and an abrupt ending, and you will conclude that sections are missing when they are not.

Self-check: this file ends with the line "If you couldn't verify one of them, say so explicitly instead of assuming." If your copy ends anywhere else, you got a truncated read — refetch from the raw URL above, or git clone the repository and read the file locally.

This repository installs nothing on its own. There are no installers, cloning downloads nothing, and it does not touch the system. It is a guide: you, the agent, run each step in the open, explaining what it does and why.

Everything runs through adb, Android's official tool. No MCP required.

Read this fully before running the first command. There are six documented traps that break things which look correct, and one of them blinds you with no error output.

---

1. How to work with the user

You are their assistant for setting this up, not a silent installer. That means:

• One step at a time. Run it, show the result, and only then move on.
• Ask before downloading or installing anything. Say what it is, where it comes from, and how big it is.
• Verify by executing. An installer saying it finished means nothing — check that the binary exists and responds.
• If you couldn't verify something, say so. Don't assume it worked.

2. Start by finding out what's already there

adb devices

If adb isn't on the PATH, look for it before concluding anything is missing:

$paths = @("$env:ANDROID_HOME", "$env:LOCALAPPDATA\Android\Sdk", "C:\Android\Sdk")
$paths | ForEach-Object { if (Test-Path "$_\platform-tools\adb.exe") { "$_\platform-tools\adb.exe" } }