據 AlphaMoat 統計,截至 2026-09,Error Guard — Control‑Plane Safety 累計下載 4,444 次、獲 8 個星標,在全部 5,078 個 AI 技能中排名第 2,187 位,在「運維安全」分類(264 個)中排名第 122 位。

累計安裝

375

累計下載

4444

星標

全站排名

#2,187

全站前 44% · 「運維安全」前 47%

平台	累計安裝	累計下載	星標	評論
ClawHub ↗	141	4248	8	2
SkillHub ↗	375	4444	8	—

各平台的計數口徑不同,統計時間不一致。

這個技能是做什麼的

設計涵蓋狀態查詢、取消全部活動任務與程序會話並清空待發佇列的緊急 flush，以及重置控制狀態並可選過載的恢復流程。命令目標是不呼叫模型、不等待 worker，且只保留任務後設資料。看門狗和子代理執行輔助仍列為未來擴充套件，不能據此認定已實現。

資料釋出於 2026-10-27

可以用來做什麼

為停滯代理任務規劃恢復控制

什麼時候用

長任務執行需要明確狀態與取消語義時

示例提示詞

以下是根據技能文件生成的示例,不代表實際執行結果。

解釋狀態、flush 和恢復的行為，說明 flush 會取消什麼，以及哪些擴充套件尚未實現。

月度資料趨勢

累計下載4444

星標8

2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。

月份	累計下載	環比	星標
2026-09	4444	—	8
2026-08	4124	+3.6%	8
2026-07	3980	—	8
2026-05	3566	—	8
2026-03	3104	—	8

SKILL.md 原文

以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。

2.7 KB · ClawHub v1.0.0

---
name: error-guard
description: >
  System safety and control-plane skill that prevents agent deadlocks and freezes.
  Provides non-LLM control commands to inspect task state, flush message queues,
  cancel long-running work, and recover safely without restarting the container.
  Use when implementing or operating long-running tasks, sub-agents, benchmarks,
  background monitors (e.g., Moltbook, PNR checks), or when the system becomes
  unresponsive and needs immediate recovery controls.
---

展開全部(共 90 行)

# error-guard

⚠️ **System‑level skill (Advanced users)**

This skill defines the **control‑plane safety primitives** for OpenClaw.
It is intentionally minimal, non‑blocking, and designed to prevent agent freezes, deadlocks, and unrecoverable states when running long‑lived or high‑risk workloads.

## Design Principles

> **Warning:** This skill operates at the agent control‑plane level.
> It should be installed only by users who understand OpenClaw’s execution model and are running workloads that can block, hang, or run for extended periods.

- **Main agent never blocks**: no long exec, no external I/O, no LLM calls.
- **Event-driven**: workers emit events; the control plane listens.
- **Fail-safe first**: recovery commands must always respond.
- **Minimal state**: track only task metadata (never payloads).

## Command Surface (Phase 1)

### /status

Report current system health and task registry state.

Returns:
- Active tasks (taskId, type, state)
- Start time and last heartbeat
- Flags for stalled or overdue tasks

Constraints:
- Must run in constant time
- Must not call any model or external API

### /flush

Emergency stop.

Immediately:
- Cancel all active tasks
- Kill active exec/process sessions
- Clear pending message queue
- Reset in-memory task registry

Constraints:
- Must always respond
- No waiting on workers
- No model calls

### /recover

Safe recovery sequence.

Steps:
1. Execute `/flush`
2. Reset control-plane state
3. Optionally reload skills/state (no container restart)

## Future Extensions (Not Implemented Yet)

- Sub-agent runner helper (event-driven)
- Task watchdogs with TTL and silence detection
- Structured event protocol (task.started, task.heartbeat, task.completed, ...)
- Back-pressure and task classes (interactive / batch / background)

## Security & Privacy

- This skill **does not** store payloads, prompts, messages, or model outputs
- Only minimal task metadata is persisted (taskId, timestamps, state)
- No API keys, credentials, or user data are read or written
- Safe to publish and share publicly

## Non-Goals

- No business logic
- No background polling loops
- No user-facing features
- No LLM reasoning paths

This skill is the **last line of defense**. Keep it small, fast, and reliable.