skills.rest
KingSharkG
KingSharkGCOMMUNITY
Explore all skills by this author →
GitHub

orchestrator-degraded

Decide between orchestrator self-correction and degraded-inline mode on dispatch failure.

Updated Apr 17, 2026
Search Tags:#workflow#recovery#orchestrator#guardrails#degraded-mode#dispatch-failure
One-click install
npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill orchestrator-degraded
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrator-degraded
Source: https://github.com/KingSharkG/ai-agents-workflow/tree/main/skills/orchestrator-degraded
Command: npx skills add https://github.com/KingSharkG/ai-agents-workflow --skill orchestrator-degraded

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrator-degraded provides decision logic for handling dispatch failures in autonomous workflows, determining whether the orchestrator can self-correct or must enter degraded-inline mode.

Core Features & Use Cases

  • Hook-block disambiguation and recovery rules to distinguish between recoverable pre-condition failures and tool unavailability.
  • Decision path to retry, self-correct, or escalate to degraded mode while preserving integrity of the orchestration state.
  • Recovery workflow that records blockers and requires explicit user waivers before continuing in degraded-inline.

Quick Start

When a dispatch fails or is blocked, trigger the degraded-mode decision path to determine whether to self-correct or enter degraded-inline.

Frequently Asked Questions about orchestrator-degraded

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

FAQPage Schema
How do I handle agent dispatch failures in an autonomous workflow?▼

When agent dispatch fails in an autonomous workflow, you can trigger a degraded-mode decision path to determine whether to self-correct the dispatch or escalate to degraded-inline mode.

What is degraded-inline mode for orchestrator recovery?▼

Degraded-inline mode is a recovery state for orchestrator dispatch failures where the system records blockers and requires explicit user waivers before continuing, ensuring normal workflow gates remain open until conditions are satisfied.

How do I distinguish between recoverable pre-condition failures and tool unavailability?▼

Hook-block disambiguation rules distinguish between recoverable pre-condition failures and tool unavailability during agent dispatch, guiding the orchestrator to retry, self-correct, or escalate to degraded mode.

Does the orchestrator require user waivers to continue in degraded mode?▼

Yes, the orchestrator requires explicit user waivers before continuing in degraded-inline mode, recording blockers and enforcing guardrails to ensure workflow gates remain open until recovery conditions are satisfied.

When should I escalate a blocked dispatch to degraded mode instead of retrying?▼

Escalate a blocked dispatch to degraded mode when hook-block disambiguation determines the failure is unrecoverable through retry or self-correction, requiring blocker documentation and user waivers to proceed safely.

Related Skills

Explore More Software Engineering Skills→
mupengi-botmupengi-bot
11

hook-engine

Manage event-driven hook triggers for skill executions with conditions and schedules.

Community
Advanced
HmbownHmbown

recovery

Assess capacity loss, apply lightest restoration, and verify baseline before resuming tempo.

Community
Intermediate
mkurmanmkurman
321

dispatching-parallel-agents

Dispatch parallel agents to investigate independent failures with isolated contexts.

Community
Advanced
spacedock-devspacedock-dev
73

fo-dispatch-recovery

Automate Claude dispatch recovery for degraded modes and context budget failures.

Official
Advanced