What problem does it solve?
After running LLM evaluations, teams often see low scores but lack a systematic way to find the root cause and decide what to fix. This Skill closes the loop from evaluation results to concrete code changes by tracing failing metrics back to specific spans and prescribing targeted fixes.
Core Features & Use Cases
- Failure Triage: Pull records with feedback scores via TruSession, filter low-scoring records, and identify which feedback functions fail most often.
- Root Cause Analysis: Map failing metrics (Context Relevance, Groundedness, Answer Relevance, Tool Selection, Plan Adherence, Logical Consistency) to specific OTEL span types and inspect trace JSON to locate the problematic step.
- Targeted Fix Recipes: Apply concrete fixes per failure mode, such as tuning retrieval k and chunking, strengthening grounding prompts, improving tool descriptions, or lowering temperature.
- Regression Verification: Re-run evaluations under a new app version, compare on the leaderboard, and flag any metric that regressed after a fix.
- Use Case: A RAG application scores 0.4 on Context Relevance. Use this Skill to trace the failure to the RETRIEVAL span, discover the chunk size is too large, apply a smaller chunking strategy, and verify the score improves in v2 without hurting Groundedness.
Quick Start
Diagnose why my RAG app's Context Relevance scores are below 0.7 and recommend fixes using my TruLens session records.