Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
General-purpose self-healing loop that learns from past failures, retries safely, and records reusable fixes.
General-purpose self-healing loop that learns from past failures, retries safely, and records reusable fixes.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill when the agent starts failing repeatedly, stalls, or keeps asking the user for steps that could be inferred from prior evidence.
Recover execution without user micromanagement Reuse previous fixes from memory/logs/tasks Escalate only with minimal unblock input when truly blocked Leave reusable evidence for future runs
Trigger when any of these appear: Same or similar error occurs 2+ times in one task Tool call fails due to argument mismatch, missing config, auth wall, or context overflow Agent claims completion without verifiable artifact Task progress stalls (no new artifact across 2 cycles)
Current task objective Latest error/output Available evidence locations (memory, tasks, logs)
Scan these in order; skip missing paths silently: memory/ (or equivalent workspace memory path) tasks/ or queue files runtime logs / channel logs skill docs (skills/*/SKILL.md) for known fallback recipes core docs (TOOLS.md, CAPABILITIES.md, AGENTS.md) Shell examples (use whichever shell is active): # PowerShell Get-ChildItem -Recurse memory, tasks -ErrorAction SilentlyContinue | Select-String -Pattern "error|blocked|retry|fallback|auth|token|proxy|timeout|context" -Context 2 # POSIX shell rg -n "error|blocked|retry|fallback|auth|token|proxy|timeout|context" memory tasks 2>/dev/null
Classify first, then act: syntax_or_args: command syntax/argument mismatch auth_or_config: key/token/env/config missing or invalid network_or_reachability: timeout, DNS, handshake, region restrictions ui_login_wall: page requires manual login/attach resource_limit: context window, rate limit, memory pressure false_done: no artifact/evidence but reported complete unknown: no confident class
Apply best-known fix from memory for same class/signature Re-run the smallest validating action Record result
Switch to alternate tool/path with lower fragility Narrow scope (smaller input, shorter query, one target) Re-run validation
Mark blocked with minimum unblock input Provide exact next action user must do (one command or one UI step) Do not loop further until new input arrives
Never auto-run destructive operations without confirmation Never log secrets/tokens in memory files Max 3 retries per blocker signature per task Prefer deterministic steps over broad speculative retries
Command mismatch on Windows: prefer native PowerShell cmdlets Token mismatch/auth failure: verify active config source and token scope WebSocket/timeouts: test reachability + proxy/no_proxy consistency Context overflow: split task into smaller units and reduce payload False completion: enforce artifact validation before final response
Works with autonomy/task-tracker skills but does not depend on them If a project has custom memory paths, adapt scan roots dynamically Keep entries short to avoid memory bloat
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.