From rag-skills
Routes RAG evaluation work across retrieval metrics, generation quality, and end-to-end evaluation frameworks. Use when measuring quality, detecting regressions, or proving changes helped.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rag-skills:evaluation-metricsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this parent skill when the main RAG problem is measuring quality, detecting regressions, or proving that a change actually helped. Route to the child skill that matches whether the failure is in retrieval, in generation, or in the evaluation harness itself.
Use this parent skill when the main RAG problem is measuring quality, detecting regressions, or proving that a change actually helped. Route to the child skill that matches whether the failure is in retrieval, in generation, or in the evaluation harness itself.
Teams ship RAG changes with no baseline, tune on vibes, and cannot tell whether a new chunker, embedding model, or prompt made things better or worse. Without metrics, retrieval and generation regressions ship silently and are only caught by users.
Measure retrieval and generation separately. Bad answers from good context are a generation problem; good answers are impossible from bad context.
Use retrieval metrics when the right chunks are missing or mis-ranked, and generation metrics when context is good but answers are wrong, unsupported, or off-topic.
Build a golden set, run the metrics on every change, and block merges that regress the baseline instead of evaluating manually.
npx claudepluginhub goodnight77/rag-skills --plugin rag-skillsGuides reception of code review feedback: verify before implementing, avoid performative agreement, push back with technical reasoning when needed.
Design banners for social media, ads, website heroes, and print with multiple art direction options and AI-generated visuals.