Skip to content
TrustedSkillsbeta
Back to all skills

Android Adb

Checked
httprunner·vlatest·frontend·MIT

This skill uses ADB to remotely control an Android device for testing and debugging, streamlining app development workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add httprunner/skills --skill android-adb -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

httprunner

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned httprunner/skills at a2f2c13619.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a2f2c13619
Manifest
android-adb/SKILL.md
Scanned
1 file, 155 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to interact with Android devices via the ADB (Android Debug Bridge) protocol. It facilitates command-line operations such as installing applications, retrieving logs, and managing device states directly from an automated environment.

When to use it

  • Automating the installation of test APKs across multiple Android devices in a CI/CD pipeline.
  • Extracting system logs or crash reports for debugging mobile application issues without physical access.
  • Performing remote device management tasks like rebooting, clearing data, or checking battery status programmatically.
  • Executing shell commands to verify UI states or automate user interactions via input methods.

Key capabilities

  • Establishes a secure connection between the host machine and Android devices.
  • Executes standard ADB commands (e.g., install, logcat, reboot, shell).
  • Manages application lifecycle events including uninstallation and package verification.
  • Retrieves real-time device information such as model, OS version, and serial number.

Example prompts

  • "Install the latest version of our banking app on all connected Android devices and verify the installation status."
  • "Pull the last 50 lines of logcat from the primary emulator and filter for 'NullPointerException' errors."
  • "Reboot the target device into recovery mode and then return it to normal operation after capturing a screenshot."

Tips & gotchas

Ensure your Android devices are properly configured with USB debugging enabled before attempting to connect. The skill requires an active ADB server running on the host machine to execute commands successfully.