android

Control paired Android phones via Hermes-Relay with taps, typing, and navigation.

114|20|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Codename-11/hermes-relay --skill android-codename-11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android
Source: https://github.com/Codename-11/hermes-relay/tree/main/skills/android
Command: npx skills add https://github.com/Codename-11/hermes-relay --skill android-codename-11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remote automation of Android devices is complex and error-prone; this skill exposes a safe, bounded surface to drive a paired Android phone from Hermes-Relay, reducing manual steps.

Core Features & Use Cases

  • Bounded tool surface to open apps, read the screen, input text, and simulate taps and swipes.
  • Pairing workflow and device connection through Hermes-Relay.
  • Safety rails and granular budgets to prevent destructive actions and ensure predictable automation.

Quick Start

Pair a phone and verify connectivity with android_ping, then begin driving actions using the android_* tools.

Frequently Asked Questions about android

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate taps and typing on an Android phone remotely?

Android automation is achieved by exposing a bounded tool surface through Hermes-Relay, allowing you to simulate taps, input text, and navigate apps on a paired device. It enforces safety rails to ensure predictable, secure remote control.

What do I need to do before I can start automating my Android device?

Before automating your Android device, you must complete a pairing workflow and verify connectivity using the android_ping command. This ensures a safe, bounded connection is established between Hermes-Relay and the phone.

Can I use this to read the screen and open apps on a paired Android phone?

Yes, you can read the screen, open apps, and simulate swipes on a paired Android phone. The skill provides a bounded tool surface designed specifically for driving these common actions safely across Android apps.

How does this approach prevent destructive actions during mobile automation?

It prevents destructive actions during mobile automation by enforcing Tier 5 safety rails and applying granular budgets. These controls ensure that Hermes-Relay operations remain secure, bounded, and predictable.

What is the best way to verify device connectivity for Android automation?

The best way to verify Android device connectivity is to use the android_ping command after initiating the pairing workflow. This confirms the Hermes-Relay connection is active before you begin driving any automation actions.

Are there limitations on what actions I can perform with bounded Android automation?

Yes, bounded Android automation limits actions to a controlled tool surface, preventing unrestricted device access. This ensures operations like text input and navigation stay within safe, granular budgets to avoid destructive behaviors.