Individual skill

rag-architecture-review

Review an existing Retrieval-Augmented Generation system and find why it underperforms. Use when asked to review or audit a RAG pipeline, diagnose wrong/ungrounded answers from a 'chat with your docs' feature, or improve an already-built knowledge assistant. Produces a staged review — ingestion, chunking, retrieval, reranking, generation, evaluation — with prioritised findings, root causes, and concrete fixes.

skills/rag-architecture-review/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RAG Architecture Review Skill

A RAG system that "hallucinates sometimes" is almost never one bug — it's a chain where the weakest stage caps
quality, and the symptom (a wrong answer) is far from the cause (a chunk that was never retrieved). This skill
reviews an existing pipeline stage by stage, isolates where quality leaks, and ranks fixes by impact so you
work the biggest lever first. (Designing a new system from scratch? Use [`rag-design-doc`](../rag-design-doc/SKILL.md).)

## Working from a brief

Given a partial description ("it uses pgvector and sometimes makes things up"), **deliver the full staged
review anyway** — infer the likely setup for each unstated stage, label the inference, and flag what to confirm.
Never withhold the review for missing detail; a labelled assumption plus "confirm this" beats a blank.

## Required Inputs
Back to top