What problem does it solve? Setting up a Telegram messaging gateway for Hermes Agent involves multiple error-prone steps: creating a bot, obtaining the correct user ID, writing protected environment files, and installing a systemd service that fails in container environments lacking a user systemd bus. ## Core Features & Use Cases - End-to-End Bot Setup: Guides creation of a Telegram bot via @BotFather, retrieval of the user ID via @userinfobot, and configuration of TELEGRAM_BOT_TOKEN and TELEGRAM_ALLOWED_USERS in ~/.hermes/.env. - Container Workaround: Provides a system-level systemd unit at /etc/systemd/system/hermes-gateway.service when hermes gateway install fails with "Failed to connect to bus: No medium found" in Docker, GCP, or VM environments. - Operations & Troubleshooting: Covers dual-service conflict resolution, TimeoutStopSec vs drain_timeout alignment, home channel setup via /sethome, and custom provider context length configuration. - Use Case: An engineer deploying Hermes Agent on a GCP container runs hermes gateway install, hits the user-bus error, and uses this Skill to install a root-level systemd service, align drain timeouts, and verify Telegram connectivity in the gateway logs. ## Quick Start Set up the Telegram gateway for Hermes Agent, including creating the bot, configuring environment variables, and working around the systemd user bus error in my container.