Build, deploy, and debug Android apps from the command line

This skill guides use of the android CLI for creating and describing projects, managing SDK packages and emulators, deploying APKs, searching Android documentation, and inspecting running application interfaces. It includes a historical help snapshot covering command families and options, with separate references for device interaction and XML-specified journey tests.

Project creation uses templates, while describe identifies metadata files containing build targets and artifact locations. SDK commands install, update, list, or remove packages. Emulator commands create, start, stop, list, and remove virtual devices. Device inspection includes PNG screen capture and a JSON layout tree, with layout differences and formatted output available in the documented snapshot.

Use it for Android development tasks that need command-line project setup, local environment information, device deployment, UI inspection, or documentation lookup. Commands depend on installed SDK state, network access, and attached hardware. This CLI must not be confused with the deprecated Android SDK tool that also used the android name.

Compare the installed version and relevant help before relying on historical flags. Documentation search results need checking against dated official documentation and the exact SDK; a returned result is not automatically current for the environment. A static review does not establish that an installation, device operation, or journey test succeeded.

The CLI must be installed and available on PATH. If missing, download the matching platform installer into a private temporary directory for inspection. Read the complete installer and secondary downloads, record its digest, and obtain confirmation before execution. Do not pipe a mutable network installer directly into a shell. This project-creation example is supplied:

android create empty-activity --name="My App" --output=./my-app

Inspect destination paths, package names, SDK targets, and device serials before running generated commands. Installation, updates, init, and skills management may change local tools or persistent configuration; review provenance, downloads, telemetry settings, licenses, and agent instructions before altering them.

Select one authorized test serial consistently for android device options and adb -s. Default device selection is unsuitable when several devices are connected. App installation or removal, SDK removal, emulator deletion, and UI actions can change data or trigger purchases, messages, and account operations. Use synthetic test accounts and scoped approval.

Screenshots and layout dumps may expose passwords, tokens, notifications, or third-party content. Store them privately, limit retention, and redact before sharing. Outputs can support debugging, but the skill's command guidance does not substitute for validation of the actual application and device workflow.