Device Streaming and Android skills – available in Android CLI

Posted by Simona Milanovic, Developer Relations Engineer

As Android developers, you have many choices when it comes to the agents, LLMs, tools, and command-line interfaces (CLI) you use for app development. Our goal is to help you build beautiful, high-quality Android apps, no matter how you choose to build. We’re announcing updates to our Android CLI command-line tooling, including the ability to access real devices through Android Device Streaming. We’re also sharing more Android skills, and giving you a deep dive into the Wear OS Compose Material 3 skill.

Android CLI for command-line development

Android CLI is our tool to make command-line interface Android development easier. It supports any AI agent or tool in building more efficiently for Android.

Along with the android-cli skill, your agents use Android CLI to create, build, test, and manage Android projects, help you set up the development environment, create and run emulators, and execute test runs.

Android Device Streaming now available in CLI

It’s important to test your app on real devices to catch issues that are hardware- or OS-specific, but sometimes you don’t have access to the ones you need. Android Device Streaming gives you access to real physical devices, remotely. Your agent can now use Android Device Streaming anywhere, through Android CLI.

The agent can interact with physical devices (as if they were plugged in over USB) over a secure ADB over SSL connection. This enables spinning up devices, deploying builds, collecting logs and traces, and even capturing screenshots headlessly—all through the terminal.

To get started, link your project, instruct your agent to list available remote devices and decide which device you want next. Read the documentation to learn more, and see the Android CLI release notes.

Grounding agents with Android skills

To bridge the gap between LLMs’ default knowledge and platform-specific standards and updates, we keep growing our Android skills repository.

Android skills are structured instructions (SKILL.md files) that ground AI agents with our official guidance from developer.android.com. Instead of relying on a model’s training cutoff, skills provide more precise and fresher data, API references and samples, and architectural patterns directly into your agent’s context.

With over 20 skills available, you can now equip your AI agents to handle more complex and specialized development tasks such as:

• Audit Play policy compliance: Audit app manifests, runtime permissions, target SDK levels, and privacy disclosures before submitting your app for Play Policy review.
• Implement Restore Credentials: Implement re-authentication across device setup and cloud restores using Jetpack Credential Manager.
• Android Intent security: Detect and prevent implicit intent hijacking, secure broadcast receivers, and validate PendingIntent declarations.
• Use Android profilers: Diagnose UI frame drops, interpret CPU/memory traces, and query trace data using natural language mapped to PerfettoSQL.
• CameraX: Replace legacy Camera1/Camera2 code with lifecycle-aware CameraX.
• Migrate Leanback to Compose for TV: Modernize Android TV experiences by transitioning from Leanback to Compose for TV.
• Integrate Media3 Cast: Connect Jetpack Media3 media sessions with Google Cast receiver devices and sync playback states.
• Integrate Play Engage SDK: Integrate the Google Play Engage SDK to publish user recommendations and cluster surfaces.
• Set up testing strategy: Configure unit test suites, Compose UI testing rules, and screenshot testing infrastructure.
• Audit R8 configuration: Optimize your app’s performance by auditing your R8 configuration.

Our Android skills are thoroughly evaluated. To understand the philosophy and methodology behind this project, as well as why all skills should come with evals, make sure to read Inside Android Skills – Built for deprecation.

Managing skills across projects and individual agent directories is pretty straightforward with Android CLI:

1. Install Android CLI
2. Run android init to install the android-cli skill
3. To list all available official skills, run: android skills list
4. To install individual skills into a single project root: android skills add wear-compose-m3 --project=.
5. To update skills, use:
6. android skills update --all
7. android skills update wear-compose-m3 (for an individual skills)

Skills are designed to be environment-agnostic. From writing code in Android Studio and Antigravity, to pairing with third-party agents like Claude and Codex, our Android skills work across your entire setup.

Skill spotlight: Wear Compose Material 3

Building for Wear OS means distinct design and development decisions: round viewports, rotary input, ambient display mode, minimizing power consumption, preferring TransformingLazyColumn, and using the AppScaffold and ScreenScaffolds containers.

Without explicit guidance, LLMs lack the understanding and knowledge of these distinct patterns that make the Wear apps really stand out and shine.

To help agents with this, we released the Wear Compose Material 3 skill (wear/wear-compose-m3).
Check out this video for more information on how powerful this skill is:

Early adopters are already seeing significant productivity impact with this skill. The engineering team at FotMob used it for tasks like modernizing their existing Wear M3-based app, migrating multiple lists to TransformingLazyColumn with ScreenScaffold content padding, ListHeader titles, SurfaceTransformation on cards and buttons, theme typography, and Wear previews.

The result? The changes compiled successfully and were verified on the emulator for scrolling, rotary, edge morphing and RTL. This enabled the team to delete their legacy wrapper, and all rotary and focus boilerplate.

The skill caught mistakes that the underlying model missed, such as forgetting to forward ScreenScaffold‘s contentPadding into the list, and using theme typography over hardcoded sp.

“One skill, one afternoon, eight lists migrated and a pile of custom rotary code gone!” – Roy Solberg, Android Tech Lead at FotMob.