adb-uiautomator
Semantic UI element detection via uiautomator2
Best use case
adb-uiautomator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Semantic UI element detection via uiautomator2
Teams using adb-uiautomator should expect a more consistent output, faster repeated execution, less prompt rewriting, better workflow continuity with your supporting tools.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
- You already have the supporting tools or dependencies needed by this skill.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/adb-uiautomator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How adb-uiautomator Compares
| Feature / Agent | adb-uiautomator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Semantic UI element detection via uiautomator2
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
---
## Quick Reference (30 seconds)
**Semantic UI element detection via uiautomator2**
**What It Does**: Automates interactions and testing for the target app.
**Core Capabilities**:
- 🚀 **App Control**: Launch and interact with app
- 🔍 **Detection**: Monitor app behavior
- ✅ **Validation**: Verify functionality
**When to Use**:
- Testing app on various devices
- Automating app interactions
- Validating app functionality
---
## Scripts
### adb-uiautomator-launch.py
Uiautomator Launch automation.
```bash
# Basic usage
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-launch.py
# With device specification
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-launch.py \
--device 127.0.0.1:5555
# JSON output
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-launch.py --json
```
---
### adb-uiautomator-check.py
Uiautomator Check automation.
```bash
# Basic usage
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-check.py
# With device specification
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-check.py \
--device 127.0.0.1:5555
# JSON output
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-check.py --json
```
---
### adb-uiautomator-test.py
Uiautomator Test automation.
```bash
# Basic usage
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-test.py
# With device specification
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-test.py \
--device 127.0.0.1:5555
# JSON output
uv run .claude/skills/adb-uiautomator/scripts/adb-uiautomator-test.py --json
```
---
## Workflows
This skill includes TOON-based workflow definitions for automation.
### What is TOON?
TOON (Task-Oriented Orchestration Notation) is a structured workflow definition language that pairs with Markdown documentation. Each workflow consists of:
- **[name].toon** - Orchestration logic and execution steps
- **[name].md** - Complete documentation and usage guide
This TOON+MD pairing approach is inspired by the BMAD METHOD pattern, adapted to use TOON instead of YAML for better orchestration support.
### Available Workflows
Workflow files are located in `workflow/` directory:
**Example Workflows (adb-uiautomator):**
- `workflow/app-launch.toon` - Launch app with uiautomator2 verification
- `workflow/element-check.toon` - Find and verify UI elements
- `workflow/functional-test.toon` - Complete app functionality testing
### Running a Workflow
Execute any workflow using the ADB workflow orchestrator:
```bash
uv run .claude/skills/adb-workflow-orchestrator/scripts/adb-run-workflow.py \
--workflow .claude/skills/adb-uiautomator/workflow/app-launch.toon \
--param device="127.0.0.1:5555"
```
### Workflow Documentation
Each workflow includes comprehensive documentation in the corresponding `.md` file:
- Purpose and use case
- Prerequisites and requirements
- Available parameters
- Execution phases and steps
- Success criteria
- Error handling and recovery
- Example commands
See the `workflow/` directory for complete TOON file definitions and documentation.
### Creating New Workflows
To create custom workflows for this skill:
1. Create a new `.toon` file in the `workflow/` directory
2. Define phases, steps, and parameters using TOON v4.0 syntax
3. Create corresponding `.md` file with comprehensive documentation
4. Test with the workflow orchestrator
For more information, refer to the TOON specification and the workflow orchestrator documentation.
---Related Skills
adb-workflow-orchestrator
TOON workflow orchestration engine for coordinating ADB automation scripts across phases with error recovery
adb-screen-detection
Screen understanding with OCR and template matching for Android device automation
adb-navigation-base
Base navigation patterns for Android device automation - gestures, waits, and UI interaction
adb-workflow-orchestrator
TOON workflow orchestration engine for coordinating ADB automation scripts across phases with error recovery
adb-screen-detection
Screen understanding with OCR and template matching for Android device automation
adb-navigation-base
Base navigation patterns for Android device automation - gestures, waits, and UI interaction
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
absinthe-subscriptions
Use when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
absinthe-resolvers
Use when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.
abramov-state-composition
Write JavaScript code in the style of Dan Abramov, co-creator of Redux and React core team member. Emphasizes predictable state management, composition over inheritance, and developer experience. Use when building React applications or managing complex state.
abp-service-patterns
ABP Framework application layer patterns including AppServices, DTOs, Mapperly mapping, Unit of Work, and common patterns like Filter DTOs and ResponseModel. Use when: (1) creating AppServices, (2) mapping DTOs with Mapperly, (3) implementing list filtering, (4) wrapping API responses.
abp-infrastructure-patterns
ABP Framework cross-cutting patterns including authorization, background jobs, distributed events, multi-tenancy, and module configuration. Use when: (1) defining permissions, (2) creating background jobs, (3) publishing/handling distributed events, (4) configuring modules.