ADB Connection
v1.0.0Control Android devices via ADB with support for UI layout analysis (uiautomator) and visual feedback (screencap). Use when you need to interact with Android apps, perform UI automation, take screenshots, or run complex ADB command sequences.
⭐ 12· 6.3k·36 current·40 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the instructions: the SKILL.md provides standard ADB, uiautomator, and screencap commands for Android automation. However, the skill metadata lists no required binaries while the instructions clearly require the adb binary (and potentially uiautomator on-device); this mismatch should be corrected or noted by the installer.
Instruction Scope
Instructions stay within the stated scope: connecting via USB/wireless, launching apps, dumping UI hierarchy, input events, and taking screencaps. The SKILL.md does instruct the agent to pull files from the device to the local working directory (e.g., /sdcard/view.xml, /sdcard/screen.png), which is expected for this functionality but is a potential data-exfiltration vector to be aware of.
Install Mechanism
No install spec or code files are present (instruction-only), so nothing is written to disk or downloaded by the skill itself. This lowers installation risk.
Credentials
The skill requests no environment variables or credentials, which is appropriate. However, it implicitly requires host-level adb access (not declared) and grants access to any connected Android device's filesystem and UI; ensure only trusted devices are connected and that the agent runtime has appropriate permissions.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent presence or modify other skills. The agent may invoke it autonomously (disable-model-invocation is false), which is platform-default — combine that with device access considerations when enabling autonomous runs.
Assessment
This SKILL.md is a straightforward ADB automation recipe and appears coherent, but before installing or using it: 1) confirm the agent runtime has the adb binary on PATH (the skill does not declare this requirement); 2) only connect devices you control or trust — the skill uses adb pull and can copy screenshots and UI dumps from devices to the agent environment; 3) review and approve any commands before allowing autonomous execution (the agent could run adb commands if allowed); 4) if you need tighter controls, require that the skill declare required binaries and document where pulled files are stored, or run the skill in an isolated environment.Like a lobster shell, security has layers — review code before you run it.
latestvk97dapkwp4ta62sgy6z0p9nhy580ebz4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.