What problem does it solve? When a containerized NanoClaw agent stops replying, fails to spawn, or silently drops messages, there is no in-container log to inspect after exit. This Skill provides a systematic debugging workflow covering host logs, session databases, mounts, and authentication so you can pinpoint where the message flow broke. ## Core Features & Use Cases - Message flow tracing: Query inbound.db and outbound.db session databases to determine whether a message reached the container, whether the agent replied, and whether delivery succeeded. - Common issue playbooks: Step-by-step diagnosis for duplicate service instances, container exit failures, OneCLI authentication errors, MCP server failures, mount problems, and stale heartbeat detection. - Operational commands: Restart session containers, rebuild the agent image, clear sessions, and run a quick diagnostic script that checks Docker, the gateway, the central DB, and duplicate processes. - Use Case: Your Telegram bot suddenly stops replying. Use this Skill to discover a second stale NanoClaw service instance is racing the delivery poll and marking messages delivered without sending them, then stop the duplicate and restore replies. ## Quick Start Ask the agent to debug why the NanoClaw container is not replying to messages and have it check the host error log and session databases.