agentleFS
MohOneXMohOneX/claude-opus-skills/literature-synthesis/SKILL.md

literature-synthesis

Skill0 starsChanged 5 months agoMITView on GitHub

Synthesizes a body of research, docs, or prior art into a coherent state-of-knowledge with conflicts and gaps made explicit. Use when surveying a field, evaluating prior art before building, reconciling conflicting sources, or producing a literature review or technical background section.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When sources conflict, don't average them — diagnose *why*: different populations, definitions, time periods, methods, or incentives?

    line 18

≈ “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

Literature Synthesis

Synthesis is not summary. A summary lists what each source says; a synthesis produces a structure those sources collectively imply, including where they disagree and what none of them answer.

Build a claim-evidence map, not a reading list

  1. Extract claims, not papers: decompose each source into discrete claims with their evidence type (theory, simulation, observational, RCT, anecdote) and strength.
  2. Cluster by claim, then see which sources support, contradict, or qualify each. The unit of synthesis is the claim, agreed/disputed across sources.
  3. Weight by evidence quality and independence: ten papers citing one original study is one data point, not ten (citation cascades manufacture false consensus).

Surface the structure of disagreement

  • When sources conflict, don't average them — diagnose why: different populations, definitions, time periods, methods, or incentives? The disagreement is often more informative than either claim.
  • Separate settled (broad independent agreement), contested (credible sources disagree), and unknown (no one has tested it). Most fields have far more "unknown" than people assume.
  • Track the provenance and recency of each claim; fields move, and the most-cited result is often the oldest, not the most correct.

Adversarial validation

  • Publication / file-drawer bias: the literature over-represents positive, novel, surprising results. The absence of a finding may mean it failed to publish, not that it's false.
  • Citation laundering: a speculative claim in an early paper becomes "established" through repeated citation without re-verification. Trace to the primary source.
  • Definitional drift: are all sources measuring the same construct, or the same word for different things?
  • Conflicts of interest / incentives: who funded it, what does the author gain from the conclusion?
  • What would the strongest dissenting expert say, and is that view represented or filtered out?

Non-obvious risks

  • Consensus among non-independent sources is not evidence; it's correlation of error.
  • The framing of the survey determines its conclusion; choosing the inclusion criteria is choosing the answer.
  • Recency bias and seminal-paper bias pull in opposite directions; name which one you're indexing on.

Output structure

Deliver: a claim-evidence matrix (claim × sources × support/contradict × evidence strength), an explicit settled/contested/unknown partition, the diagnosis of each major disagreement, the gaps no source addresses, and the synthesized position with its confidence and what would change it.

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.