LaunchKit · 2026
Back to Skills

mobilerun

Control real Android phones through the Mobilerun API.

0
0 downloads
by @johnmalek312

Setup & Installation

openclaw skills install @johnmalek312/mobilerun

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install mobilerun

What This Skill Does

Controls real Android devices through the Mobilerun API. Supports screenshots, UI tree reading, tapping, swiping, typing, and app management. Works with personal phones via the Portal APK or cloud-provisioned devices.

Works on real hardware without rooting or emulators, giving AI agents access to the actual app environment rather than a simulated one.

When to use it

  • Filling out mobile forms automatically
  • Extracting data from apps that lack a web version
  • Testing Android app flows without manual interaction
  • Automating repetitive daily tasks on a phone
  • Navigating multi-screen workflows in any installed app

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: Open the Settings app and find the Wi-Fi network name

AGENT
  1. 1Call GET /devices to find a ready device
  2. 2Call PUT /devices/{id}/apps/com.android.settings to open Settings
  3. 3Take a screenshot via GET /devices/{id}/screenshot to see current state
  4. 4Read UI tree via GET /devices/{id}/ui-state?filter=true to locate the Wi-Fi option
  5. 5Tap the Wi-Fi element using its center coordinates
  6. 6Take another screenshot and read the connected network name from the UI tree
OUTPUT

Returns the current Wi-Fi network name shown in Settings

Requirements

Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.

MOBILERUN_API_KEY environment variable (prefixed dr_sk_, from https://cloud.mobilerun.ai/api-keys)Android phone with Droidrun Portal APK installed, or a cloud device on a paid plan