Root-cause a relevance bug in tokenization/analysis/mapping before touching the ranking formula. Reach for this on a no-match or wrong-match bug.
Scanned 9/23/2026
Skills Directorynpx -y skills add mcorbett51090/RavenClaude --skill fix-analyzer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fix Analyzer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mcorbett51090-fix-analyzer)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: fix-analyzer
description: "Root-cause a relevance bug in tokenization/analysis/mapping before touching the ranking formula. Reach for this on a no-match or wrong-match bug."
---
# Skill: Fix analyzer
A relevance bug is usually a mapping/analyzer bug, not a ranking tweak (§3 #2).
## Step 1 — Reproduce the match failure
Trace how the query and document are analyzed/tokenized (§3 #2).
## Step 2 — Check the mapping
Field types, analyzers, stemming, synonyms — does it match as intended? (§3 #2)
## Step 3 — Secure recall first
Fix matching/query expansion so the right doc is retrieved (§3 #5).
## Step 4 — Re-measure relevance
Confirm the fix on NDCG, don't trust the spot-check (§3 #1).
## Output
An analyzer/mapping root-cause and recall fix with the relevance re-measured. 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!
