self-healing-wrapper

Wrap unattended scripts to capture failure output and trigger AI diagnosis.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill self-healing-wrapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-healing-wrapper
Source: https://github.com/kriscendobot/garden/tree/main/skills/self-healing-wrapper
Command: npx skills add https://github.com/kriscendobot/garden --skill self-healing-wrapper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the issue of silent script failures in unattended environments by capturing failure output, diagnosing the root cause, and proposing or executing fixes automatically.

Core Features & Use Cases

  • Durable Failure Capture: Automatically hashes failure logs into a content-addressable store to preserve evidence without bloating token costs.
  • Task-Specific Diagnosis: Invokes AI responders tailored to the specific script role rather than relying on generic, fleet-wide error reporting.
  • Automated Escalation: Routes fixes to the gardener inbox, improvement logs, or the job board based on the severity and durability requirements of the task.

Quick Start

Wrap your existing background script with the self-healing-wrapper to automatically capture errors and trigger AI-driven diagnosis upon failure.

Frequently Asked Questions about self-healing-wrapper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate failure recovery for unattended background scripts?

Automate failure recovery by wrapping your script with a standardized wrapper that captures failure output and triggers task-specific AI diagnosis to propose or execute fixes automatically. This prevents silent script failures in unattended environments.

How does content-addressable logging work for script error handling?

Content-addressable logging hashes failure logs into a durable store to preserve evidence without bloating token costs. This ensures failure data is captured efficiently for AI diagnosis while keeping operational overhead low.

Can I use self-healing wrappers with systemd services and state machines?

Yes, the wrapper applies to automated background jobs, systemd services, and state machines requiring robust error handling. It provides standardized failure capture and self-correction capabilities for these unattended execution environments.

What is the best way to prevent silent script failures in automated jobs?

Prevent silent failures by implementing a wrapper that captures errors, diagnoses root causes with task-specific AI responders, and routes fixes to gardener inboxes or job boards based on severity and durability requirements.

How does AI diagnosis handle script errors without invoking generic reporting?

AI diagnosis invokes task-specific responders tailored to the specific script role rather than relying on generic fleet-wide error reporting. This ensures targeted root cause analysis and proposed fixes for your automated background jobs.

Does the wrapper support throttled AI invocation for debugging?

Yes, the wrapper satisfies requirements for throttled AI invocation to prevent excessive calls during failure diagnosis. It ensures automated escalation routes fixes appropriately based on task severity and durability requirements.