Agent skill

OpenGUI Android Control

by Core-Mate in Core-Mate/OpenGUI

Drives locally connected Android phones through OpenGUI screenshots and allowlisted actions, one observed step at a time, for app, game and multi-device tasks.

Custom licenceAuto-check passedMobile

Install OpenGUI Android Control

skills CLI
$ npx skills add Core-Mate/OpenGUI --skill control -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Core-Mate/OpenGUI control --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Core-Mate/OpenGUI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/deepseek-harness-plugin/skills/control .claude/skills/control && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
control
GitHub stars
1.8k
Token cost
~788 tokens
SKILL.md length
410 words
Files
2
Skills in repo
7
Repo updated
First seen
Licence
Custom licence

At a glance

Drives locally connected Android phones through OpenGUI screenshots and allowlisted actions, one observed step at a time, for app, game and multi-device tasks.

  • Works in 6 steps: Call opengui_list_devices. Explain USB… → Call opengui_open_session with one to… → Call opengui_observe before the first… → …
  • Opening and testing an app on a connected Android phone
  • SKILL.md covers Route the task, Phone loop and External side effects
  • Calls node and adb

What it does

Activates by intent: any request that targets a phone, an Android app, a mobile game or several devices, without the user needing to say OpenGUI. It uses the OpenGUI MCP tools when present, or a node CLI adapter in skills-only installs, and never bypasses the adapter with raw adb shell commands. Browser-only work goes to the native Codex Browser instead.

The phone loop is: list devices, open a session with one to four device ids, observe a screenshot, perform exactly one action at a time using the newest observation id, and close the session when done, with a cancel call if the user asks to stop. Multi-device sessions pass a device id on every call and freeze the device set. It stops on stale observations, repeated lack of progress, operation limits, authorization problems or disconnects, and a device wall URL can be opened for monitoring.

When your agent uses it

  • Opening and testing an app on a connected Android phone
  • Claiming rewards in a mobile game
  • Running the same steps on several phones
  • Monitoring multiple devices on a device wall

Example prompts

  • “Open the settings app on my connected Android phone and turn on dark mode.”
  • “Claim today's reward in the mobile game on both phones.”
  • “Test the login screen of my app on the attached device.”

Requirements

  • An Android phone connected over USB with debugging authorized
  • The OpenGUI MCP tools or its node CLI adapter

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Call opengui_list_devices. Explain USB authorization or connection errors rather than guessing.
  2. Call opengui_open_session with one to four selected device ids. Omit ids only when exactly one authorized phone is connected.
  3. Call opengui_observe before the first mutation. Treat the returned screenshot pixels as the only valid coordinate space.
  4. Perform exactly one opengui_act at a time with the newest observationId, then inspect the returned observation. Use tight target bounds…
  5. Open the returned deviceWallUrl in the native Codex Browser when the user asks to monitor devices or when a multi-device wall helps.
  6. Always call opengui_close_session after success. Call opengui_cancel immediately when the user asks to stop or when continuing would be…

What it can do on your machine

Read from SKILL.md and the folder at commit ad6d57f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node
    • adb

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OpenGUI Android Control loads about 788 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 410 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~74
When it runs · the whole SKILL.md, loaded when a task matches
~788

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 410 words (~788 tokens).

“Use the OpenGUI MCP tools when they are available. In a public Skills-only installation, resolve the plugin root as two directories above this file and invoke node /lib/codex-cli.js '' instead. The CLI returns screenshot files under its private state directory…”

— opening of SKILL.md by Core-Mate, Custom licence
name
control

Read the full SKILL.md on GitHub

Files

SKILL.md and 1 other file in deepseek-harness-plugin/skills/control of Core-Mate/OpenGUI.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit ad6d57f

Compare with similar skills

OpenGUI Android Control next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OpenGUI Android Control compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OpenGUI Android Control this skillCore-Mate/OpenGUI1.8k—~788Automated safety check: PassCustom licence
Magicnet Device DebuggingLIghtJUNction/MagicNet185—~2.9kAutomated safety check: NotesMIT
Scrcpy GotchasJuanCF/scrcpy-mcp112—~5.8kAutomated safety check: PassMIT
Generate Appclaw Flowappclawhq/AppClaw116—~3.4kAutomated safety check: NotesApache-2.0
Spock AdbWahdanZ/SpockAdb114—~3.3kAutomated safety check: PassApache-2.0
Aaalice Runtime VerifyAaalice233/Aaalice_NAI_Launcher187—~963Automated safety check: PassMIT

Similar skills

  • Magicnet Device Debugging

    LIghtJUNction/MagicNet

    Debug and verify MagicNet on a real Android root device. An agent skill from LIghtJUNction/MagicNet.

    185 GitHub stars~2.9k tokensUpdated today
    MobileAuto-check: notes
  • Scrcpy Gotchas

    JuanCF/scrcpy-mcp

    A skill your agent uses when interacting with Android devices via scrcpy-mcp tools (tap, swipe, inputtext, keyevent, uidump, uifindelement, appstart, etc.).

    112 GitHub stars~5.8k tokensUpdated 14 days ago
    MobileAuto-check passed
  • Generate Appclaw Flow

    appclawhq/AppClaw

    Generate YAML flow files for AppClaw mobile automation. An agent skill from appclawhq/AppClaw.

    116 GitHub stars~3.4k tokensUpdated 1 mo ago
    MobileAuto-check: notes
  • Spock Adb

    WahdanZ/SpockAdb

    Debug Android apps on a connected device or emulator through the Spock ADB MCP server (tools named android).

    114 GitHub stars~3.3k tokensUpdated yesterday
    MobileAuto-check passed
  • Aaalice Runtime Verify

    Aaalice233/Aaalice_NAI_Launcher

    用户要求自动化运行验收、界面操作、截图检查或双端 UI 测试时,自动启动或复用 Aaalice NAI Launcher 热重载会话,通过项目级 Dart/Flutter MCP 验证应用;Android 系统界面按需使用 ADB。

    187 GitHub stars~963 tokensUpdated yesterday
    MobileAuto-check passed
  • Use Appclaw CLI

    appclawhq/AppClaw

    Use the AppClaw CLI to run YAML flows, start the interactive TUI shell, explore apps, record/replay sessions, configure devices, and troubleshoot.

    116 GitHub stars~4.6k tokensUpdated 1 mo ago
    MobileAuto-check: notes

More from Core-Mate/OpenGUI

  • OpenGUI Bootstrap

    Core-Mate/OpenGUI

    Installs, configures and runs OpenGUI's backend and Android client from a plain-language request, running the repo's own setup scripts and asking the user only for physical phone steps or secrets.

    1.8k GitHub stars~1.7k tokensUpdated today
    Auto-check: notes
  • OpenGUI Installer for DSH

    Core-Mate/OpenGUI

    Installs and verifies the latest stable OpenGUI release in a DeepSeek Harness web profile on macOS without disturbing existing plugins or settings.

    1.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Lets a coding agent list, run, pause, resume or cancel natural-language tasks on an Android phone through the OpenGUI backend instead of raw ADB commands.

    1.8k GitHub stars~2.6k tokensUpdated today
    Auto-check: notes
  • Controls an authorized local Android phone, or shows its live read-only video feed, for phone app tasks and Android UI checks on macOS.

    1.8k GitHub stars~762 tokensUpdated today
    Auto-check passed
  • Completes an already-authorized task on a real Android phone or a macOS iOS simulator one screenshot-driven action at a time.

    1.8k GitHub stars~7.2k tokensUpdated today
    Auto-check passed
  • OpenGUI Plugin Installer

    Core-Mate/OpenGUI

    Installs or upgrades the standalone OpenGUI plugin for Codex or WorkBuddy on macOS from verified prebuilt GitHub releases, checking the SHA-256 before running anything.

    1.8k GitHub stars~1k tokensUpdated today
    Auto-check passed

Questions about OpenGUI Android Control

What does OpenGUI Android Control do?

Drives locally connected Android phones through OpenGUI screenshots and allowlisted actions, one observed step at a time, for app, game and multi-device tasks. Activates by intent: any request that targets a phone, an Android app, a mobile game or several devices, without the user needing to say OpenGUI. It uses the OpenGUI MCP tools when present, or a node CLI adapter in skills-only installs, and never bypasses the adapter with raw adb shell commands.

When should I use OpenGUI Android Control?

OpenGUI Android Control fits situations like: opening and testing an app on a connected Android phone; claiming rewards in a mobile game; running the same steps on several phones; monitoring multiple devices on a device wall.

How do I install OpenGUI Android Control in Claude Code?

Run `npx skills add Core-Mate/OpenGUI --skill control -a claude-code`. Or copy the skill folder (deepseek-harness-plugin/skills/control in Core-Mate/OpenGUI) into .claude/skills/control in your project. Claude Code loads it when a task matches its description.

How do I install OpenGUI Android Control in Codex?

Run `npx skills add Core-Mate/OpenGUI --skill control -a codex`. Or copy the skill folder (deepseek-harness-plugin/skills/control in Core-Mate/OpenGUI) into .agents/skills/control in your project. Codex loads it when a task matches its description.

Can I use OpenGUI Android Control in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Core-Mate/OpenGUI --skill control -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/control, .gemini/skills/control, .github/skills/control and .opencode/skills/control in your project.

What does OpenGUI Android Control need to run?

Going by SKILL.md and its folder, OpenGUI Android Control needs the command-line tools its instructions call (node and adb). Our summary lists: An Android phone connected over USB with debugging authorized; The OpenGUI MCP tools or its node CLI adapter.

Does OpenGUI Android Control access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is OpenGUI Android Control safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OpenGUI Android Control use?

OpenGUI Android Control has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does OpenGUI Android Control use?

About 788 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OpenGUI Android Control?

Skills that share tags, products or a category with OpenGUI Android Control: Magicnet Device Debugging (LIghtJUNction/MagicNet, 185 stars), Scrcpy Gotchas (JuanCF/scrcpy-mcp, 112 stars), Generate Appclaw Flow (appclawhq/AppClaw, 116 stars) and Spock Adb (WahdanZ/SpockAdb, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OpenGUI Android Control?

Core-Mate (a GitHub organization) maintains it in Core-Mate/OpenGUI, which has 1,815 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.

Source: Core-Mate/OpenGUI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.