error-recovery

Handle timeouts, API errors, and rate limits in multi-agent workflows.

7|4|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/MadAppGang/magus --skill error-recovery-madappgang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-recovery
Source: https://github.com/MadAppGang/magus/tree/main/plugins/multimodel/skills/error-recovery
Command: npx skills add https://github.com/MadAppGang/magus --skill error-recovery-madappgang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides battle-tested patterns for handling failures gracefully in multi-agent workflows, ensuring that temporary errors, timeouts, or partial failures don't derail entire processes.

Core Features & Use Cases

  • Timeout Handling: Manages external model timeouts (>30s) with retry or skip options.
  • API Failure Recovery: Recovers from common API errors (401, 500, network issues, rate limits) with appropriate retry strategies.
  • Partial Success: Continues workflows even when some agents fail, proceeding with available results.
  • User Cancellation: Gracefully handles Ctrl+C, saving partial results and logging progress.
  • Missing Tools/Credits: Falls back to embedded models when external tools like claudish are missing or API credits are exhausted.
  • Use Case: When running a multi-model code review, if one of the external models times out or returns a 500 error, this skill ensures the workflow doesn't stop, instead proceeding with the successful reviews and informing the user about the failures.

Quick Start

Use the error-recovery skill to handle a timeout when calling an external model.

Frequently Asked Questions about error-recovery

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

FAQPage Schema
How do I handle external model timeouts in multi-agent AI workflows?

Handle external model timeouts in multi-agent workflows by implementing retry or skip options. This skill manages delays exceeding 30 seconds, allowing the process to proceed with available results instead of derailing entirely.

What is the best way to recover from API rate limiting and 5xx errors in AI pipelines?

Recover from API rate limiting and 5xx errors in AI pipelines by applying exponential backoff strategies. This approach automatically manages retry intervals to ensure workflow resilience and production readiness during transient network failures.

How does graceful degradation work when external API credits are exhausted?

Graceful degradation when API credits are exhausted works by falling back to embedded models. This ensures the workflow continues processing with available local resources rather than failing due to missing external dependencies.

Can I save partial workflow results if a user cancels a multi-agent process?

Yes, you can save partial workflow results if a user cancels a multi-agent process. The mechanism gracefully handles user cancellations like Ctrl+C, logging progress and preserving successful outputs before exiting.

How do I continue multi-agent workflows when some API calls fail with 401 errors?

Continue multi-agent workflows when API calls fail with 401 errors by proceeding with partial success. The workflow skips the failed agents and continues using the successful results, informing the user about the failures.