restore

Restore autonomous coding agent fleets after service interruptions by requeueing orphaned jobs and resetting worker pools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill resolves fleet-wide operational stalls caused by API outages, network partitions, or quota limits, ensuring that stalled agents and orphaned jobs are automatically recovered without manual intervention.

Core Features & Use Cases

  • Fleet Reactivation: Automatically resets failed worker units and restores the gardener pool to a healthy state.
  • Orphaned Job Recovery: Requeues stale in-flight claims and processes dead-letter messages to ensure no work is lost.
  • Poisoned Job Resolution: Identifies and redispatches jobs that failed due to transient errors, clearing the maintainer inbox.

Quick Start

Run the restore skill to reactivate the worker pool and recover all stalled fleet operations after a service outage.

Frequently Asked Questions about restore

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

FAQPage Schema
How do I recover orphaned jobs in an autonomous coding agent fleet after an outage?

Recovering orphaned jobs in an autonomous coding agent fleet involves requeueing stale in-flight claims and processing dead-letter queues. This ensures state consistency and task completion after system-wide service interruptions without manual intervention.

What is the best way to reset crashed worker units and restore a gardener pool?

Resetting crashed worker units and restoring a gardener pool is best handled through automated worker pool resets. This fleet reactivation process targets dead-letter queues and crashed units to return the system to a healthy state.

When do I need to redispatch poison messages from a dead-letter queue?

Redispatching poison messages from a dead-letter queue is necessary when jobs fail due to transient errors like API outages or network partitions. Identifying and clearing these poisoned jobs ensures the maintainer inbox stays empty and operational flow continues.

How does idempotent recovery work for stalled autonomous coding agents?

Idempotent recovery for stalled autonomous coding agents works by safely resetting worker pools, requeueing claims, and redispatching poison messages. This prevents duplicate task execution while guaranteeing state consistency across the fleet after quota limits or outages.

Can I use automated fleet recovery for stalls caused by network partitions and API quota limits?

Yes, automated fleet recovery resolves stalls caused by network partitions and API quota limits. The process targets orphaned job claims and crashed worker units to automatically restore operational continuity without requiring manual intervention.

What are the limitations of automated worker pool resets for fleet recovery?

Automated worker pool resets rely on idempotent procedures to safely handle transient errors and orphaned claims. Severe systemic state corruption beyond dead-letter queues might still require manual intervention to fully ensure fleet consistency.