What problem does it solve? Messaging platforms connected to Hermes sometimes stop delivering messages, ignore senders, or risk reply loops, and it is hard to tell whether the cause is transport, authorization, or adapter filtering. This Skill provides a structured diagnostic workflow to isolate the failing layer and verify fixes with real command output. ## Core Features & Use Cases - End-to-end path verification: Checks gateway service, platform server, webhook listener, health endpoints, and adapter logs before assuming config is wrong. - Platform-specific runbooks: Covers Telegram forum session scoping for /sessions and /resume, BlueBubbles/iMessage self-message loop guards, and memory-context injection probe handling. - Loop-prevention guidance: Recommends outbound-ID-based echo filtering instead of blanket isFromMe skips, plus IPv4/IPv6 localhost pitfalls on macOS. - Use Case: A user texts Hermes from their own iMessage identity and gets no reply; the Skill guides checking webhook registration, the outbound-ID loop-guard cache, and gateway logs to restore delivery without disabling loop protection. ## Quick Start Ask the assistant to troubleshoot why Telegram messages to Hermes are not getting replies and have it verify the gateway, webhook, and authorization path step by step.
