Use the storm skill to research RAG evaluation frameworks. Produce the standard HTML artifact bundle and focus on how an engineering team should choose among RAGAs, ARES, and RAGChecker.

| Stage | Artifact | What changes |
|---|---|---|
| Direct outline | direct_gen_outline.html | Topic-only structure before retrieval |
| Refined outline | storm_gen_outline.html | Adds dimensions and framework distinctions found in the papers |
| Draft article | storm_gen_article.html | Writes the evidence-backed comparison with inline citations |
| Polished article | storm_gen_article_polished.html | Tightens the decision guidance and adds verification notes |
| Perspective | Question theme | Query theme | Primary sources used |
|---|---|---|---|
| Basic fact writer | Why RAG needs modular evaluation | Original RAG architecture and provenance | 1 |
| Evaluation methodologist | Which dimensions can be evaluated automatically | RAGAs and ARES evaluation dimensions | 2 |
| Systems diagnostician | How to localize retrieval versus generation failures | RAGChecker diagnostic metrics | 1 |
| Engineering lead | How the frameworks differ operationally | Cross-source synthesis | 3 |
The example uses four primary papers: