burner-phone

Control Android devices via ADB, Termux, or emulators using vision-guided coordinate actions.

53|6|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/SouthpawIN/burner-phone --skill burner-phone-southpawin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: burner-phone
Source: https://github.com/SouthpawIN/burner-phone/tree/main
Command: npx skills add https://github.com/SouthpawIN/burner-phone --skill burner-phone-southpawin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill removes the friction of manually operating an Android device for screenshots, taps, typing, and basic media actions by providing a unified, automation-friendly control layer.

Core Features & Use Cases

  • Universal Android control across backends: Operates via Termux, ADB-only devices, or Android emulators.
  • Vision feedback loop for UI automation: Take a screenshot, analyze it to get precise coordinates, then act (tap/swipe/type) and verify with a follow-up screenshot.
  • Device interaction primitives for mobile workflows: Wake/unlock, capture camera (when supported), record/play audio, and launch apps to support mobile app testing or AI companionship.

What problem does it solve?

You want reliable mobile device automation (for testing, assistance, or delegated tasks) without needing to hard-code screen coordinates yourself.

Quick Start

Tell your agent to: take a screenshot, run vision to find the Settings button coordinates, then tap those coordinates and confirm the result with a second screenshot.

Frequently Asked Questions about burner-phone

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

FAQPage Schema
How do I automate Android UI interactions without hard-coding screen coordinates?

Android UI automation can use a vision feedback loop to screenshot the screen, extract target coordinates automatically, then execute ADB input actions and verify results with a follow-up screenshot.

Can I control an Android emulator using ADB and vision-guided screen capture?

Yes, Android emulators are fully supported through ADB input commands, allowing you to capture screenshots, extract UI coordinates using vision analysis, and trigger taps or swipes.

Does Android device automation work with Termux or do I need a connected computer?

Android device automation works directly on the device using Termux without a connected computer, while also supporting ADB-only devices and emulators for remote control workflows.

How do I take a screenshot and tap a specific button on an Android device for mobile app testing?

Mobile app testing uses a screenshot to capture the current screen state, passes the image to a vision helper for coordinate extraction, sends an ADB tap command to those coordinates, and takes a verification screenshot.

What basic device interactions are available for Android automation workflows?

Android automation workflows support device interaction primitives including screen wake and unlock, camera capture, audio recording and playback, app launching, and UI actions like tap, swipe, and type.

Do I need to configure device settings before running ADB automation tasks?

Yes, ADB automation tasks require a YAML device configuration file to define connection parameters and backend type before executing vision-guided screen capture and input actions.