Error Recovery Automation Skill

This skill provides patterns for automating the detection and recovery of common OpenClaw errors: gateway unresponsiveness, browser service failures, cron scheduler issues, and other recurring problems. It builds on health‑monitoring and system‑diagnostics by adding automated recovery workflows that can be triggered by cron jobs, heartbeat checks, or external monitoring.

When to use

• A service (gateway, browser, cron) fails intermittently and you want to automate its restart.
• You are setting up proactive monitoring and need a recovery plan beyond just detection.
• You want to reduce the manual steps required when “Läuft alles?” reveals a failure.
• You need to ensure critical OpenClaw components stay running with minimal user intervention.
• You are asked to “create a skill for error recovery automation” (this is that skill).

Core patterns

1. Error Detection Patterns

Before automating recovery, you must reliably detect the error. Use these detection methods: