hermes-relay-doctor

Automate end-to-end health checks for the Hermes-Relay bridge stack.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smoke-test the Hermes-Relay bridge stack — checks relay health, phone connection, bridge channel, accessibility service, and screenshot capture in one pass.

Core Features & Use Cases

  • Runs a sequential smoke-test of the full bridge stack and reports pass/fail with fix hints for each check.
  • Verifies core integration points before issuing Android-related tool calls or diagnostics.
  • Use case: when the bridge isn't functioning, the phone isn't pairing, or the screenshot functionality is failing, you run this to confirm stack health.

Quick Start

Run hermes-relay-doctor to execute the full bridge stack health checks.

Frequently Asked Questions about hermes-relay-doctor

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

FAQPage Schema
How do I run an end-to-end health check for an Android bridge stack?

An end-to-end health check for an Android bridge stack verifies relay health, phone connectivity, bridge channel, accessibility service, and screenshot capture in one sequential pass, reporting pass/fail with actionable guidance.

Why does my Android phone bridge connectivity fail to pair or respond?

Bridge connectivity fails when the relay health endpoint, bridge channel, or accessibility service is down. Run a sequential bridge stack smoke-test to identify the failing integration point and get actionable fix hints.

What's the best way to troubleshoot screenshot capability issues on an Android bridge?

To troubleshoot screenshot capability, run an end-to-end diagnostic that verifies the /screen and /screenshot endpoints, confirming stack health before issuing further Android-related tool calls.

How do I verify bridge health endpoints before running Android diagnostics?

Verify bridge health endpoints by running an automated smoke-test that checks /health, /bridge/status, /ping, /current_app, /screen, and /screenshot, returning pass/fail with actionable guidance for each endpoint.

Can I diagnose accessibility service status without checking the full bridge stack?

Diagnosing accessibility service status without checking the full bridge stack is not recommended. Automated sequential smoke-tests verify core integration points including accessibility service and phone connection together for accurate diagnosis.