What problem does it solve? Running a deployed Hermes Agent in container or cloud environments involves tricky operational hurdles: terminal token redaction corrupting credential writes, missing user systemd buses breaking gateway installation, cross-instance webhook tunnels dropping silently, and messaging platform pairing codes failing to deliver due to rate limits. ## Core Features & Use Cases - Credential Management: Write API tokens to .env using Python token assembly to bypass terminal redaction, and manage credential pools via the hermes auth CLI. - Messaging Gateway Setup: Connect Telegram (BotFather token flow) and WeChat (iLink QR login) platforms, configure allowed users, and set home channels. - Cross-Instance Communication: Bridge two Hermes instances via SSH reverse tunnels or GCP IAP tunnels with HMAC-signed webhook POSTs. - Gateway Service Management: Work around missing user systemd buses in containers with system-level units, align TimeoutStopSec with drain timeouts, and restart gateways blocked from inside their own process tree via cron. - Use Case: Your Telegram gateway on a GCP VM fails hermes gateway install with "Failed to connect to bus" — this Skill walks you through creating a system-level systemd unit, verifying connectivity, and setting up a keepalive cron job. ## Quick Start Ask the agent to set up the Telegram gateway for your Hermes instance and troubleshoot why the gateway service will not install on your container.