failure-analyzer

Cluster eval failures by root cause into a structured failure report.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill failure-analyzer-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: failure-analyzer
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/failure-analyzer
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill failure-analyzer-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an eval run produces failures, raw pass/fail counts and flat lists of failing examples do not explain what is actually wrong. This Skill turns eval results into an actionable diagnosis by grouping failures by root cause and surfacing regressions first. ## Core Features & Use Cases - Regression Detection: Diffs current results against the prior run and always ranks newly broken, previously-passing examples as the top category. - Root-Cause Clustering: Groups failures into categories like policy violations, dropped sub-issues, vague deferrals, tool-call errors, tone mismatch, retrieval misses, and looping behavior. - Subagent Delegation: Hands clustering to a failure-triage subagent when more than 30 examples fail, preserving context on large result sets. - Use Case: After baseline-runner writes eval/results/baseline.json with 40 failures, run this Skill to get eval/failure_report.md showing 5 regressions, 12 tool-call errors, and 8 dropped sub-issues, each with example IDs and a suggested fix direction. ## Quick Start Analyze the failures in eval/results/baseline.json and write a clustered failure report to eval/failure_report.md.

Frequently Asked Questions about failure-analyzer

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

FAQPage Schema
How do I analyze why my LLM eval failed?▼

Run the failure analysis on the eval results file such as eval/results/baseline.json. The Skill pulls every failing example, clusters them by root cause, and writes eval/failure_report.md with counts, example IDs, and suggested fix directions per category.

How do I detect regressions between two eval runs?▼

The Skill diffs pass/fail status per example ID against the prior results file. Any example that passed before and fails now is flagged as a regression and always listed as the first category in the report.

What failure categories does eval failure analysis cover?▼

Failures are clustered into policy or faithfulness violations, dropped sub-issues, vague deferrals, tool-call errors, tone mismatch, retrieval misses for RAG tasks, and trajectory or looping behavior. Only categories with actual hits appear in the report.

When does failure analysis delegate to a subagent?▼

Delegation to the failure-triage subagent happens only when more than 30 examples fail. Smaller failure sets are clustered directly inline so context is not lost to a subagent handoff.

Does failure analysis automatically fix the agent's prompt or code?▼

No. The Skill only diagnoses failures and proposes fix directions as hypotheses for the user to evaluate. It never edits the agent's prompt or code itself.