Search

PythonReactSEOPDF
OpenClaw

adb-controller

Control an Android device via ADB. Use when the user asks to control an Android device, tap, swipe, input text, or perform actions via adb. Automatically uses the adbServer configured in openclaw.json and takes screenshots.

fengyang03170 source installs☆ 0 Repository stars

Installation

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.

SkillHub CLI

skillhub install fengyang0317/adb-controller

Inspect the source and compatibility requirements, then follow its installation steps.

Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.

View source ↗Guides

Skill instructions

ADB Controller

This skill allows you to execute ADB (Android Debug Bridge) commands on a connected Android device and automatically retrieve a screenshot of the result.

Configuration

The user can configure the target ADB device/server in their openclaw.json (this is automatically read by the script):

{
  "skills": {
    "entries": {
      "adb-controller": {
        "adbServer": "192.168.1.100:5555" // or device serial
      }
    }
  }
}

Usage

To run an ADB command, execute the provided Python script:

python3 ~/.openclaw/workspace/skills/adb-controller/scripts/run_adb.py shell input tap x y

You can pass any standard ADB arguments to the script. For example:

  • python3 .../run_adb.py shell input text "hello"
  • python3 .../run_adb.py shell input keyevent 26 (Power button)
  • python3 .../run_adb.py shell swipe 500 1000 500 500

Workflow (Mandatory)

  1. Understand the user's intent and determine the correct ADB command.
  2. Execute the user's requested action using the run_adb.py script via the exec tool.
  3. The script will output the path to a newly captured screenshot.
  4. Send the Image: You MUST use the message tool (with action="send" and media="<path-to-screenshot>") to send the resulting screenshot to the user, allowing them to see the outcome of the action. Do not just output the file path.

Source information

Source
github
Repository
openclaw/skills
Path
skills/fengyang0317/adb-controller
Version
—
Commit
2a3099cd21c05c3d76d4f6366d3801e6bf047ba3
Classification source
rules
Status
active
Visibility
public

These signals come from indexed source analysis and may lag behind changes. Check the current source files.

Extracted content

SKILL.md
# ADB Controller

This skill allows you to execute ADB (Android Debug Bridge) commands on a connected Android device and automatically retrieve a screenshot of the result.

## Configuration

The user can configure the target ADB device/server in their `openclaw.json` (this is automatically read by the script):
```json
{
  "skills": {
    "entries": {
      "adb-controller": {
        "adbServer": "192.168.1.100:5555" // or device serial
      }
    }
  }
}
```

## Usage

To run an ADB command, execute the provided Python script:

```bash
python3 ~/.openclaw/workspace/skills/adb-controller/scripts/run_adb.py shell input tap x y
```

You can pass any standard ADB arguments to the script. For example:
- `python3 .../run_adb.py shell input text "hello"`
- `python3 .../run_adb.py shell input keyevent 26` (Power button)
- `python3 .../run_adb.py shell swipe 500 1000 500 500`

## Workflow (Mandatory)

1. Understand the user's intent and determine the correct ADB command.
2. Execute the user's requested action using the `run_adb.py` script via the `exec` tool.
3. The script will output the path to a newly captured screenshot.
4. **Send the Image:** You MUST use the `message` tool (with `action="send"` and `media="<path-to-screenshot>"`) to send the resulting screenshot to the user, allowing them to see the outcome of the action. Do not just output the file path.

Related skills

OpenClaw

13-Day Sprint Method

galizki

Productivity system based on Maya calendar with 13 natural tones for project management and personal development

OpenClaw

1password

daggerkun007

Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.