Separate retrieval failure from generation failure by measuring recall@k before touching the model. Reach for this first on wrong answers.
Scanned 9/23/2026
npx -y skills add mcorbett51090/RavenClaude --skill diagnose-retrieval --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Diagnose Retrieval?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-diagnose-retrieval)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: diagnose-retrieval
description: "Separate retrieval failure from generation failure by measuring recall@k before touching the model. Reach for this first on wrong answers."
---
# Skill: Diagnose retrieval
If the right passage isn't retrieved, no prompt or bigger model recovers it (§3 #1).
## Step 1 — Measure recall@k
Is the relevant passage in the top-k? via `ai_rag_engineering_calc.py retrieval-eval` (§3 #1).
## Step 2 — Split the failure mode
Low recall = retrieval bug; high recall + wrong answer = generation/grounding bug (§3 #1 #7).
## Step 3 — Check hybrid
Try BM25 + vector fusion on the failing queries, especially keyword-heavy ones (§3 #6).
## Step 4 — Fix the binding stage first
Retrieval before generation — don't swap the model on a retrieval bug (§3 #1).
## Output
A failure-mode split (retrieval vs generation) with the first fix named. Traverse Tree 2 in the decision-trees file.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!