Error Recovery

Name: Error Recovery
Availability: InStock
Author: strategicmilk

Classify worker task errors and apply recovery actions like retries or reassignment.

Updated Mar 3, 2026

Search Tags:#orchestration #error-recovery #fallback #retry #task-classification #worker-agent

Ready to run

npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill error-recovery-strategicmilk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Error Recovery
Source: https://github.com/StrategicMilk/Vetinari-Orchestrastor/tree/main/vetinari/skills/catalog/worker/error-recovery
Command: npx skills add https://github.com/StrategicMilk/Vetinari-Orchestrastor --skill error-recovery-strategicmilk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The worker often encounters runtime failures that waste tokens and stall pipelines. Without systematic classification and targeted recovery, every error requires manual intervention or blind retries.

Core Features & Use Cases

Error classification into transient, decomposition, delegation, unsolvable, and policy‑violation categories.
Recovery strategies such as exponential backoff retries, task re‑decomposition, agent reassignment, user notification for unsolvable cases, and policy‑compliant reformulation.
Budget checks to prevent runaway token usage and enforce retry limits.
Pattern detection to spot systemic failures and trigger escalation to the Foreman. Use case: When a build task exceeds token limits, the skill redirects the task to the Foreman for re‑decomposition instead of endless retries.

Quick Start

Ask the worker to recover the failed task by providing the error details and let it handle the appropriate recovery steps.

Frequently Asked Questions about Error Recovery

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

FAQPage Schema

How do I handle task execution failures and prevent blind retries in agent orchestration?▼

Task execution failures in agent orchestration can be handled by classifying error types into transient, decomposition, delegation, unsolvable, or policy-viololation categories, then applying targeted remediation strategies like exponential backoff retries or task re-decomposition instead of blind retries.

What is the best way to retry transient worker agent errors without wasting tokens?▼

The best way to retry transient worker agent errors without wasting tokens is to apply exponential backoff retries combined with budget checks, which prevent runaway token usage and enforce strict retry limits during orchestration.

How do I classify and recover from policy violation errors during task orchestration?▼

Policy violation errors during task orchestration are classified as a specific error category and recovered through policy-compliant reformulation, ensuring that worker agent tasks remain compliant with safety policies after the failure.

Why does a build task exceed token limits and stall the pipeline during orchestration?▼

A build task exceeds token limits and stalls the pipeline due to unclassified runtime failures triggering endless retries, which can be resolved by redirecting the task to the Foreman for re-decomposition instead of continuing the loop.

Can I use error classification to detect systemic failures and escalate tasks to a Foreman?▼

Yes, error classification includes pattern detection to spot systemic failures across worker agent tasks, automatically triggering an escalation to the Foreman when budget checks detect repeated token usage or token limit exceedances.

How do I manage unsolvable task errors and notify users during agent orchestration?▼

Unsolvable task errors during agent orchestration are managed by classifying them into a dedicated unsolvable category, which triggers a user notification action to inform the user that the task cannot be completed automatically.