error-guard for Openclaw

A control-plane safety skill designed to prevent agent deadlocks and provide emergency recovery commands for long-running workloads.

amar1432
v1.0.0
Feb 1, 2026
8
4.2k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install error-guard

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install error-guard using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is error-guard?

error-guard serves as a critical safety layer for Openclaw Skills, acting as a non-blocking control plane that monitors system health. Unlike standard skills that rely on LLM reasoning, this tool provides deterministic commands to manage task states, inspect registries, and recover from unresponsive states without requiring a full container restart. It is an essential utility for developers building complex, long-lived, or high-risk agentic workflows where reliability is paramount.

The skill is built on fail-safe principles, ensuring that the main agent never blocks on external I/O or model calls. By maintaining a minimal state and tracking only task metadata, it provides a robust last line of defense for your automation environment.

error-guard Use Cases

  • Managing long-running background tasks like web scraping or large-scale data processing.
  • Recovering from agent freezes during sub-agent orchestration or recursive loops.
  • Monitoring the health of background monitors such as Moltbook or PNR checks.
  • Executing emergency stops to clear pending message queues and reset task registries.

How error-guard Works

  1. The skill acts as an event-driven listener that tracks task metadata without blocking the main agent execution.
  2. Users or sub-agents invoke non-LLM commands like /status to inspect the current state of active tasks and heartbeats.
  3. If a deadlock or freeze is detected, the /flush command kills active processes and clears the message queue.
  4. The /recover sequence performs a reset of the control-plane state and reloads configuration without killing the container environment.

error-guard Setup

To install this safety-critical skill within your environment, ensure you are running a compatible version of the framework and add the skill via your configuration file or CLI. Use the following command to integrate it with your existing Openclaw Skills:

openclaw install error-guard

After installation, you can verify the status of your environment by running the /status command in your agent console.

error-guard Data Schema & Taxonomy

error-guard is designed with a minimal state footprint to ensure speed and security. It avoids storing sensitive payloads, prompts, or model outputs, focusing purely on lifecycle metadata.

Field Type Description
taskId String Unique identifier for the current execution unit.
type String The category of the task being performed (e.g., exec, sub-agent).
state Enum Current status: active, stalled, or overdue.
heartbeat Timestamp The last recorded activity from the worker process.

error-guard Advanced Features

  • Constant-time execution for recovery commands to ensure responsiveness even during high CPU load.
  • Non-LLM reasoning path ensures recovery commands work even when the model API is unresponsive.
  • Support for future TTL-based task watchdogs and silence detection to automate recovery.
  • Deterministic task registry reset which clears in-memory queues without data loss in external volumes.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*