v1.0.0 to v1.1.0

45 added, 11 removed. Audit A to A.

---
name: self-healing-error-recovery
- description: "GENIUS-style self-healing for errors"
- version: 1.0.0
+ description: >
+ Diagnoses failures and retries with alternate strategies. Use when commands
+ fail, tools error, or the user says heal this error, self recover, fix failu
+ re automatically. Stores lessons for future tasks. Triggers: heal this error
+ , selfrecover, fix failure automatically, retry smart.
+ version: 1.1.0
author: Stijnman
license: MIT
metadata:
- hermes:
- tags: []
- related_skills: []
+ grok:
+ tags: [heal this error, self recover, fix failure automatically, retry smart]
+ related_skills: [knowledge-graph-builder, semantic-memory-manager, bottleneck-resolver]
+ compatibility: Grok agent; optional MCP and shell access
---
# Self Healing Error Recovery
- ## Overview
- GENIUS-style self-healing for errors. Triggers: 'heal this error', 'self recover', 'fix failure automatically'. Diagnose with knowledge-graph, repair loop, sandbox retries. 76%+ recovery. Stores lessons in semantic memory.
-
## When to Use
- - heal this error, self recover, fix failure automatically
- ## Common Pitfalls
- - No action specified yet.
+ - User says **heal this error** or task matches this capability
+ - User says **self recover** or task matches this capability
+ - User says **fix failure automatically** or task matches this capability
+ - User says **retry smart** or task matches this capability
+
+ ## Workflow
+
+ 1. Capture error message, command, and environment context.
+ 2. Classify: transient / config / permission / logic / dependency.
+ 3. Try up to 3 recovery strategies (retry, alternate path, dependency fix).
+ 4. If recovered, summarize fix. If not, escalate with diagnosis.
+ 5. Record lesson: error pattern -> successful fix.
+
+ ## Integrations
+
+ - `knowledge-graph-builder`
+ - `semantic-memory-manager`
+ - `bottleneck-resolver`
+
+ ## Error Handling
+
+ | Failure | Response |
+ |---------|----------|
+ | Destructive command failed | Do not auto-retry deletes; require HITL. |
+ | Same error 3x | Stop retrying; report root cause. |
+ | Permission denied | Never escalate privileges; ask user. |
+
+ ## Gotchas
+
+ - Read-only diagnosis first; mutate only after classification.
+
+ ## Example
+
+ **Input:** User request matching triggers above.
+ **Output:** Structured result per workflow with integrations invoked as needed.