What problem does it solve? Telegram bots and gateways hosted on GCP frequently disconnect from the Telegram API (15-30 times per day), causing stuck "typing" indicators, delayed messages, and missed updates. This Skill stabilizes the connection by routing Telegram traffic through Cloudflare WARP instead of the unstable GCP native network. ## Core Features & Use Cases - Traffic Routing via WARP: Adds sing-box route rules that direct Telegram API domains and IP ranges (149.154.x.x, 91.108.x.x) through the warp-out WireGuard outbound. - SOCKS5 Proxy Configuration: Sets TELEGRAM_PROXY to the local sing-box socks-in endpoint (127.0.0.1:10808) so the gateway uses the WARP path. - Verification Workflow: Provides log-based checks to confirm the proxy is detected and that network-error reconnect counts drop. - Use Case: A Hermes gateway on GCP loses Telegram connectivity dozens of times daily; after applying this routing, it runs 29+ hours without a single disconnect. ## Quick Start Ask the agent to configure sing-box so that all Telegram API traffic goes through the WARP outbound and update the gateway proxy environment variable accordingly.