agentleFS
TakaGotoTakaGoto/rag-learning-academy/.claude/skills/paper-review/SKILL.md

paper-review

Skill24 starsChanged 20 days agoMITView on GitHub

Walk through a RAG research paper together

29 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use paper-writing.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MLNLP-WorldSkill

    paper-writing

    学术论文写作检查与优化助手。基于 MLNLP-World 社区整理的论文写作技巧,帮助检查和优化学术论文。Use when: (1) 检查论文 LaTeX 格式和排版, (2) 优化公式符号使用, (3) 改进图表设计, (4) 润色英文学术表达, (5) 检查参考文献格式, (6) 投稿前终稿检查, (7) 用户询问论文写作技巧或规范。

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user provides a paper title or URL (e.g., /paper-review "Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks"), use …

    line 12
  2. Distinctive:

    Ask the learner which paper interests them or recommend one based on their current module.

    line 30
  3. Distinctive:

    Before diving in, give the learner context:

    line 34
  4. Distinctive:

    When was it published and why did it matter at that time?

    line 36
  5. Distinctive:

    Do not just summarize; explain and connect to practical knowledge

    line 101

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Paper Review: Understand RAG Research Papers

Break down RAG research papers into understandable pieces, connecting academic innovations to practical applications the learner can use in their pipeline.

Step 1: Identify the Paper

If the user provides a paper title or URL (e.g., /paper-review "Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks"), use that. Otherwise, suggest papers from a curated list organized by topic:

Foundational Papers

  • "Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks" (Lewis et al., 2020)
  • "Dense Passage Retrieval for Open-Domain Question Answering" (Karpukhin et al., 2020)
  • "REALM: Retrieval-Augmented Language Model Pre-Training" (Guu et al., 2020)

Chunking and Retrieval

  • "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks" (Reimers & Gurevych, 2019)
  • "ColBERT: Efficient and Effective Passage Search via Contextualized Late Interaction" (Khattab & Zaharia, 2020)

Advanced RAG

  • "Self-RAG: Learning to Retrieve, Generate, and Critique through Self-Reflection" (Asai et al., 2023)
  • "RAPTOR: Recursive Abstractive Processing for Tree-Organized Retrieval" (Sarthi et al., 2024)

Evaluation

  • "RAGAS: Automated Evaluation of Retrieval Augmented Generation" (Es et al., 2023)

Ask the learner which paper interests them or recommend one based on their current module.

Step 2: Set Context

Before diving in, give the learner context:

  • What problem was this paper trying to solve?
  • When was it published and why did it matter at that time?
  • What should they pay attention to while reading?
  • How does it connect to what they have already learned?

Step 3: Section-by-Section Walkthrough

Break the paper down into digestible sections:

Abstract and Introduction

  • Summarize the core claim in one sentence
  • What gap in existing work does this address?
  • What is the proposed solution at a high level?

Background and Related Work

  • What prior work does this build on?
  • What are the key concepts the reader needs to understand?
  • Fill in any knowledge gaps the learner might have

Methodology / Approach

  • How does the proposed system work? Explain the architecture.
  • Draw an ASCII diagram of the system if helpful.
  • Translate mathematical notation into plain English where needed.
  • Connect each component to practical RAG concepts the learner knows.

Experiments and Results

  • What did they test and how?
  • What were the key results? Present the important numbers.
  • Were the baselines fair? Any concerns about the evaluation?

Discussion and Limitations

  • What are the acknowledged limitations?
  • What are the unacknowledged limitations you can spot?
  • What follow-up work did this inspire?

Step 4: Practical Takeaways

The most important step. Extract actionable insights:

  1. What can you use today? Specific techniques or ideas applicable to the learner's pipeline.
  2. Key insight: The one idea from this paper that changes how you think about RAG.
  3. Implementation hints: How would you implement the core idea in a practical system?
  4. What to skip: Parts of the paper that are specific to their experimental setup and less useful in practice.

Step 5: Connect to Curriculum

Map the paper's concepts to specific curriculum modules and lessons. If the learner has not covered a prerequisite concept, briefly explain it or suggest the relevant /lesson.

Step 6: Discussion Questions

Pose 2-3 thought-provoking questions:

  • "How would this approach perform on your specific use case?"
  • "What trade-offs does this design make that you might handle differently?"
  • "If you could extend this work, what would you try?"

Discuss the learner's thoughts. This builds critical thinking about research.

Suggest 2-3 relevant next steps using slash commands:

  • /explain — deep-dive into a specific concept from this paper you want to understand better
  • /build — implement the paper's core technique in your own RAG pipeline
  • /challenge — take on a challenge that applies the ideas from this paper

Guidelines

  • Assume the learner has not read the paper — make it accessible
  • Do not just summarize; explain and connect to practical knowledge
  • Be honest about limitations — not every paper is a breakthrough
  • Encourage the learner to read the original paper after the walkthrough
  • Track paper reviews in progress/papers-reviewed.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.