gaia-debugging
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix. Use when a GAIA benchmark run reports a failed/incorrect task_id and you need to root-cause it before resubmitting.
Profile →npx skills add ruvnet/ruflo --skill gaia-debugging --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GAIA Debugging Skill When a GAIA question fails, systematically diagnose the root cause and propose a targeted fix. ## When to use - A specific `task_id` returns the wrong answer or times out - Pass-rate dropped between two runs and you need to find the regression - You want to understand why a particular question class is consistently failing ## Failure mode taxonomy | Code | Mode | Symptom | Fix direction | |------|------|---------|--------------| | TG | Tool Gap | Agent lacks a required tool (no image OCR, no PDF reader) | Add tool to catalogue | | RM | Reasoning Miss | Agent has the right data but draws wrong conclusion | Improve system prompt, add CoT instruction | | EB | Extraction Bug | Answer is in the trace but `FINAL_ANSWER:` regex fails | Fix answer extraction pattern | | LI | Loop Issue | Agent loops (re-asks same tool call) and hits turn limit | Increase max-turns or add loop-detection | | DS | Dataset Shift | Ground truth differs from what web currently shows | Flag for HAL dataset audit | | AT | API Timeout | Tool call times out; agent never gets the result | Increase per-turn timeout | ## Diagnostic workflow ### Step 1 — Load the question trace ```bash # Find the
- When to use
- Failure mode taxonomy
- Diagnostic workflow
- Step 1 — Load the question trace
- Step 2 — Classify the failure
- Step 3 — Re-run with extended logging
- Step 4 — Apply targeted fix
- Step 5 — Verify fix and store pattern
- Quick reference: tool catalogue check
- Pattern storage
Find the result for the task_id in the latest run
node -e "
const r = JSON.parse(require('fs').readFileSync('$RESULTS'));
const q = r.results.find(x => x.task_id === '$TASK_ID');
node v3/@claude-flow/cli/bin/cli.js gaia-bench run \
Re-run the single question
node … gaia-bench run --task-id $TASK_ID --models $MODEL --output json
If now passing, store the pattern
npx @claude-flow/cli@latest memory store \
const { createDefaultToolCatalogue } = require('./v3/@claude-flow/cli/src/benchmarks/gaia-tools/index.js');What does the gaia-debugging skill do?
Diagnose why a GAIA question failed — extract trace, classify failure mode, and propose a fix. Use when a GAIA benchmark run reports a failed/incorrect task_id and you need to root-cause it before resubmitting.
How do I install it?
Run `npx skills add ruvnet/ruflo --skill gaia-debugging --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ruvnet/ruflo, a repository with 67,015 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.