eval-and-improve

Runs the Agno eval suite, diagnoses failures, and fixes agent instructions until all cases pass.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/martin-cousseau/refund-arena --skill eval-and-improve-martin-cousseau
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eval-and-improve
Source: https://github.com/martin-cousseau/refund-arena/tree/main/backend/.agents/skills/eval-and-improve
Command: npx skills add https://github.com/martin-cousseau/refund-arena --skill eval-and-improve-martin-cousseau

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Eval suites fail for many reasons — weak agent instructions, wrong assertions, judge variance, environment drift — and manually triaging each failure is slow and error-prone. This Skill runs the eval suite, diagnoses every failure against a structured symptom table, applies in-scope fixes, and loops until the suite is green. ## Core Features & Use Cases - Guided eval execution: Run cases by tag (smoke, release, live), by name, or with JSON output carrying judge reasoning, with clear preconditions for Postgres, venv, and API keys. - Structured failure diagnosis: A symptom-to-cause-to-fix table covers judge misses, missing or extra tool calls, flaky runs, HITL gate pauses, teardown cleanup errors, and sweep guard trips. - Scoped repair loop: Fixes are limited to agent instructions, tools, and model config in agents/ and teams/, plus correcting genuinely wrong assertions — never weakening a case to force a pass. - Use Case: An overnight scheduled eval run fails. Use this Skill to locate the failing case in eval history, reproduce it with --name, diagnose the root cause, tighten the agent's routing rule, and re-run until the release tag exits 0. ## Quick Start Run the eval suite, diagnose any failing cases, fix the agent instructions that caused them, and keep iterating until everything passes.

Frequently Asked Questions about eval-and-improve

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

FAQPage Schema
How do I run only specific eval cases in an Agno eval suite?▼

Run a single case with python -m evals --name <case>, or select groups by tag using --tag smoke, --tag release, or --tag live. Add --list to preview which cases a selector picks without running them, and --json-output for machine-readable results with judge reasoning.

How do I fix an eval that fails because the agent missed a tool call?▼

A missing tool call usually means the agent's routing rule is too weak or the case is too narrow. Strengthen the instruction in agents/<slug>.py, or broaden expected_tool_calls if the assertion itself was wrong — never weaken a case just to make it pass.

Why does my eval pass alone but fail in the full suite?▼

This pattern usually indicates a transient flake or rate limiting (HTTP 429). Re-run the case alone, then the suite; if 429s persist, back off. Cases that flip PASS/FAIL across runs without changes point to judge variance — make the criteria more falsifiable.

What causes a 'cleanup:' error in eval teardown?▼

A cleanup error means a teardown hook could not delete something the case created. Hard-delete the leftover rows by id using eval_db.delete_component, ScheduleManager, or notes.delete, and do not modify the agent or the case to work around it.

When should I not edit an eval case to make it pass?▼

Never weaken a case to force a green result — edit a case only when the assertion itself was wrong. Read both the agent response and judge_reason first, and verify the fix earns the pass: the tool actually fired and the rubric cannot be met by a shortcut.