What problem does it solve? Restarting the OpenClaw gateway with raw launchctl commands can leave broken cron symlinks, stale state, and silent channel failures. This Skill provides a canonical five-step restart sequence that cleans transient cron state, re-applies symlinks, kickstarts the launchd service, and verifies channel recovery. ## Core Features & Use Cases - Safe Restart Sequence: Removes the transient cron jobs file, re-applies GNU stow symlinks, and kickstarts the com.openclaw.gateway launchd service in the correct order. - Crash-Loop Detection: Inspects launchd state after restart and fails explicitly if the gateway is still crash-looping or the health endpoint is unreachable. - Channel Verification: Checks recent logs for Telegram, Slack, or WhatsApp reconnection events and emits a JSON status summary for callers. - Use Case: After editing openclaw.json or rotating channel secrets, run this restart procedure to ensure the gateway picks up changes and all messaging channels reconnect cleanly. ## Quick Start Ask the agent to restart the OpenClaw gateway safely after your config change and verify that all channels reconnect.