workflow-debugger

Diagnoses failed Gorgon workflow runs by analyzing checkpoint state, agent logs, and budget traces.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill workflow-debugger-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-debugger
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/agents/analysis/workflow-debugger
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill workflow-debugger-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a multi-agent Gorgon workflow fails mid-run, hangs, or exhausts its token budget, finding the root cause requires manually digging through checkpoint databases, agent logs, and output contracts. This Skill automates that forensic analysis and produces an evidence-based diagnosis with actionable fixes. ## Core Features & Use Cases - Failure Diagnosis: Locates the exact failure point in the checkpoint database, examines agent outputs against expected schemas, checks per-agent budget consumption, and classifies the root cause into a defined failure taxonomy (contract violation, budget exhaustion, timeout, hallucination, and more). - Post-Mortem Analysis: Analyzes completed workflow runs to identify wasted tokens, slow stages, and optimization opportunities with estimated savings. - Actionable Reporting: Produces a structured debug report with evidence, fix options ordered by ROI with effort estimates, and a single recommended fix. - Use Case: A workflow fails at step 4 of 7 with a cryptic error. Run the diagnosis to discover the upstream agent returned a partial result missing a required key, then receive three fix options ranging from a 15-minute quick patch to a systemic schema-validation fix. ## Quick Start Ask the agent to diagnose why workflow run run_2026-02-12_001 failed using the checkpoint database at .gorgon/checkpoints.db and the agent logs in .gorgon/runs.

Frequently Asked Questions about workflow-debugger

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

FAQPage Schema
How do I diagnose why a multi-agent workflow failed?▼

Run the diagnose_failure operation with the workflow run ID, checkpoint database path, and agent log directory. The skill locates the failure point, examines agent outputs against expected schemas, checks budget consumption, and classifies the root cause with supporting evidence.

How to analyze token budget usage across workflow agents?▼

Query the budget_log table in the checkpoint database to get per-agent tokens_used versus token_budget percentages. The post_mortem operation automates this, producing a stage breakdown with waste estimates and optimization opportunities.

What are common causes of multi-agent workflow failures?▼

Workflows fail for eight classified reasons: contract violations, budget exhaustion, timeouts, dependency failures, context overflow, hallucination, checkpoint corruption, and external infrastructure errors. Most failures are logic or contract issues rather than infrastructure problems.

Can this tool fix a failed workflow automatically?▼

No. The skill is strictly read-only and forensic; it never modifies workflow state, checkpoints, or agent outputs. It produces fix options with effort estimates ordered by ROI, but applying fixes is left to the user or other workflow-design skills.

When should I not use workflow-level diagnosis?▼

Skip it for debugging application code inside a repository, auditing repository tech debt, designing new workflows, or simple single-step tool errors like file-not-found. Those cases are better handled directly or by dedicated debugging and auditing skills.