kuri-android

Automate Android device taps, swipes, text input, and app control via CLI.

349|18|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/justrach/kuri --skill kuri-android
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kuri-android
Source: https://github.com/justrach/kuri/tree/main/.claude/skills/kuri-android
Command: npx skills add https://github.com/justrach/kuri --skill kuri-android

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates direct control of Android devices from the CLI, enabling scripted interactions with taps, swipes, and app management.

Core Features & Use Cases

  • Drive Android devices and emulators via the kuri android subcommand, including taps, swipes, text input, screenshots, and app control.
  • Dump the UI tree, capture PNG screenshots, list connected devices, and launch/terminate apps by package.
  • Operate across multiple devices or emulators with a native Zig adb wire-protocol driver and no on-device runtime dependencies.

Quick Start

Use kuri android to connect to a device, verify connectivity with list-devices, and capture a screenshot.

Frequently Asked Questions about kuri-android

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

FAQPage Schema
How do I automate Android device testing from the command line?

Automate Android device testing from the command line by using a native CLI driver to script taps, swipes, text input, and app lifecycle management across connected devices and emulators.

Can I control multiple Android devices without installing the adb binary on the host machine?

Yes, you can control multiple Android devices without the adb binary by using a native Zig wire-protocol client that communicates directly with devices, ensuring portability and reliability without shelling out.

How do I capture a screenshot and dump the UI tree from an Android emulator via CLI?

Capture PNG screenshots and dump the UI tree from an Android emulator via CLI by executing the respective subcommands to extract visual and structural hierarchy data for automated testing.

Does Android UI automation work across both physical devices and emulators?

Android UI automation works across both physical devices and emulators, handling device enumeration and direct interactions uniformly through a single wire-protocol driver with no on-device runtime dependencies.

What is the best way to script UI interactions for Android apps without on-device dependencies?

Script UI interactions for Android apps without on-device dependencies by utilizing a CLI driver that implements the adb wire protocol to handle taps, swipes, and app management directly from the host.