agentleFS
KhaledSaeed18KhaledSaeed18/dotclaude/skills/academic/lit-review-synthesis/SKILL.md

lit-review-synthesis

Skill5 starsChanged 4 months agoMITView on GitHub

Build a literature review as an argument from paper-reader notes: cluster the notes into themes, surface agreements, tensions, and methodological patterns, locate the gap the thesis fills, and draft the review chapter so that each paragraph advances a claim rather than summarising one paper. Every citation comes from the notes and the .bib. Use when the reading is done and the related-work or background chapter needs writing, or when a draft review reads like an annotated bibliography.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Read every note and tabulate, in research/evidence-matrix.md:

    line 18
  2. Distinctive:

    Write the outline as claims, one line per paragraph:

    line 39
  3. Distinctive:

    Prefer synthesis sentences that cite several keys ("Three studies in introductory courses report reductions of 20 to 30% \cite{a,b,c}") …

    line 55
  4. Distinctive:

    Every number comes from a note's *Evidence* section, unrounded.

    line 57
  5. Very specific:

    Run citation-verifier on the draft (Level 3 especially), then humanize.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

A literature review is an argument that ends in the gap. It is not a sequence of "Smith (2023) did X. Jones (2024) did Y." Every paragraph makes a point about the field, and papers appear as evidence for that point. This skill works only from paper-reader notes so that every sentence about a paper is traceable.

Inputs

  1. research/notes/*.md (the notes; refuse to proceed with fewer than five, and say why).
  2. research/QUESTION.md (the research question the review must lead to).
  3. references.bib (keys must match note front matter).
  4. Target length and the department's expected structure, if any.

Step 1: build the evidence matrix

Read every note and tabulate, in research/evidence-matrix.md:

keyyeartypesettingmethodmain findinglimitationrelevancethemes

The themes column is filled in Step 2. This table is a thesis artifact in its own right (appendix material) and lets the student see the field at a glance.

Step 2: find the structure

Cluster notes into three to six themes. Good themes are claims about the field, not topic labels: "Rule-based feedback scales but does not transfer across assignments" rather than "Rule-based approaches". Test each theme:

  • It has at least two papers.
  • Its papers can be compared on some dimension (method, setting, result).
  • It moves the argument toward the gap.

Then map the tensions: where do papers disagree, and is the disagreement explained by method, setting, or time? Disagreements are the most valuable paragraphs in a review.

Note methodological patterns across the field (everyone uses dataset D; nobody reports variance; evaluations are all with novices). These become the "limitations of prior work" paragraph and often are the gap.

Step 3: outline

Write the outline as claims, one line per paragraph:

1. Intro: scope of the review and how sources were found (from search-log.md).
2. Theme A claim. Evidence: smith2023, lee2022. Tension: chen2021 finds the opposite, in setting S.
3. ...
N-1. Methodological limitations across the field.
N. The gap, stated as the research question, and what this thesis does about it.

Get the student's agreement on the outline before drafting; restructuring a drafted chapter costs a week.

Step 4: draft

  • Paragraph = claim, evidence, interpretation. The claim sentence has no citation; the evidence sentences do.
  • Cite by key only (\cite{smith2023feedback} or [@smith2023feedback]); never write an author-year string by hand.
  • Prefer synthesis sentences that cite several keys ("Three studies in introductory courses report reductions of 20 to 30% \cite{a,b,c}") over one-paper sentences.
  • Quote only from a note's Quotable section, with its location.
  • Every number comes from a note's Evidence section, unrounded.
  • Hedge to the strength of the evidence, once per claim: "suggests" for one small study, "shows" for replicated results.
  • End with the gap paragraph that restates the research question in the field's terms.

Step 5: check

Run citation-verifier on the draft (Level 3 especially), then humanize. Report the ratio of synthesis sentences to single-paper sentences; below 1:2 the chapter is still an annotated bibliography.

Output

chapters/02-related-work.md or .tex (the student's choice), the evidence matrix, and the agreed outline at the top of the file as a comment.

Attribution

The argument-first structure is adapted from lit-review by bethww (MIT).

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.