Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Add escalation examples for rate-limit, validation, and login timeout
What This Skill Does
Defines a strict error-handling workflow for agents: identify the failure, attempt two bounded fixes, then escalate with plain-language communication. Prevents retry loops, duplicate outbound messages, and raw error dumps reaching the user. Includes hard stops for destructive or security-boundary situations.
Enforces a two-attempt ceiling on retries and requires verified outcomes before reporting success, preventing runaway loops and false "done" confirmations that other ad-hoc error handling skips.
When to use it
- Recovering from a rate-limited publish without spamming retries
- Handling a calendar event creation error with date/timezone fixes
- Escalating a timed-out login flow to the user for OAuth confirmation
- Preventing duplicate posts when an external publish action fails
- Reporting a failed file write as pending rather than falsely done
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Post my announcement to the blog
- 1Attempt to publish the post via the configured tool
- 2Receive rate-limit rejection, identify failure in one sentence
- 3Retry immediately as fix #1
- 4Retry with a delayed slot as fix #2
- 5Stop retrying, send escalation message: what failed, what was tried, what happens next
Dit faalde: publish werd afgewezen door rate-limit. Ik heb 1) direct retry en 2) delayed retry geprobeerd. Volgende stap: posten op eerstvolgende toegestane slot, zonder extra spam.