Automate this: /mobile-release:doctor reports whether this CLI and the rest of the Android toolchain are installed; /mobile-release:bootstrap uses android describe for artifact discovery. All of this skill is unattended-safe — it neither signs nor publishes.

Drive the android CLI to do Android work from the terminal. Prefer it over raw sdkmanager/avdmanager/adb — it is one binary, its output is machine-readable, and it blocks until operations actually finish. Never assume it is installed.

Confidence marks used throughout this skill: [verified] — read off a primary vendor source on 2026-08-05. [snippet] — secondary source only, plausible but unconfirmed. [unverified] — not confirmed anywhere; run the check given before relying on it. See Verification notes at the end for what was and was not confirmed.

Process:

Check for the binary: command -v android. If missing, install it — see Install. If the user cannot install it, switch to Fallback: legacy tooling and use sdkmanager/avdmanager/adb for the rest of the session.
Run android init once per environment, and android info to confirm the SDK location.
Run android describe --project_dir=<path> before any build step. It emits the JSON that tells you where build targets and output artifacts (APK/AAB) actually land. Do not guess artifact paths.
Install only the SDK packages the project needs with android sdk install.
Boot a device with android emulator start <avd> — it returns when the device is ready.
Deploy with android run --apks=<paths from step 3>.
Inspect the running UI with android layout, not screenshots. Use android screen capture only when a human needs to see pixels.
Resolve any Android API or behavior question with android docs search / android docs fetch instead of answering from memory.
To sign, bundle, or upload — stop here and switch skills. See What this CLI cannot do.

android-cli