android-cli-ci

Configures Android SDK in CI using the official `dbt` toolchain and automated workflows.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/premex-ab/claude-marketplace --skill android-cli-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-cli-ci
Source: https://github.com/premex-ab/claude-marketplace/tree/main/plugins/android-cli/skills/android-cli-ci
Command: npx skills add https://github.com/premex-ab/claude-marketplace --skill android-cli-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the complexity of setting up Android build infrastructure in CI by replacing the legacy cmdline-tools workflow with Google’s newer agent-first android CLI.

Core Features & Use Cases

  • CI/CD-ready install and SDK provisioning: Installs the android launcher and uses it to install required SDK packages (platforms, build-tools, platform-tools) in a non-interactive way.
  • Gradle workflow preservation: Keeps Gradle as the build system, guiding you to run ./gradlew assembleDebug and related tasks without changing your app build logic.
  • Caching strategy for fast pipelines: Recommends what to cache (CLI state, SDK path, Gradle caches) and how to key caches for stability.
  • Emulator instrumentation support: Covers when/how to enable emulator usage for instrumentation tests (notably KVM needs on Linux).
  • Migration guidance from legacy CI: Explains how to convert common sdkmanager/avdmanager/emulator-runner patterns, including package-name syntax changes.

Quick Start

Use the android-cli-ci skill to migrate your CI pipeline to install Android SDK components via android sdk install platforms/android-34 build-tools/34.0.0 platform-tools and then run your Gradle build such as ./gradlew --no-daemon assembleDebug.

Frequently Asked Questions about android-cli-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install Android SDK packages in CI without using sdkmanager?

Install Android SDK packages in CI using Google's android CLI with slash-based syntax, such as 'android sdk install platforms/android-34 build-tools/34.0.0 platform-tools', replacing legacy sdkmanager flows for non-interactive provisioning.

What is the best way to migrate Android CI from cmdline-tools to the android CLI?

Migrate Android CI from cmdline-tools by adopting the android CLI for SDK installation and converting package-name syntax, while preserving Gradle as the build system to run tasks like './gradlew assembleDebug' without altering app build logic.

Does Android emulator instrumentation testing work on Linux CI runners?

Android emulator instrumentation testing works on Linux CI runners but requires enabling KVM support for the emulator to function properly during instrumentation tests.

How should I cache Android SDK and Gradle state in GitHub Actions or GitLab CI?

Cache Android SDK and Gradle state in CI by keying caches for CLI state, SDK paths, and Gradle caches to ensure deterministic, stable pipelines across GitHub Actions, GitLab CI, CircleCI, Bitrise, Jenkins, and Buildkite.

Can I run Gradle builds with the android CLI without replacing Gradle itself?

You can run Gradle builds with the android CLI without replacing Gradle itself by using the CLI solely for SDK provisioning and executing standard wrapper commands like './gradlew --no-daemon assembleDebug' for the actual build.

Why does my android CLI SDK installation fail interactively in CI pipelines?

Android CLI SDK installation fails interactively in CI pipelines because CI environments require deterministic, non-interactive execution via the install script or premex-ab/setup-android-cli to properly provision packages.