agentleFS
cellrishi-codecellrishi-code/claude-skills-atlas/skills/research/literature-synthesizer/SKILL.md

literature-synthesizer

Skill5 starsChanged 44 days agoMITView on GitHub

Use when synthesizing multiple research papers or supplied sources into themes, disagreements, evidence gaps, and research opportunities.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not invent missing bibliographic or experimental details.

    line 32
  2. Distinctive:

    Use this skill when the task involves literature synthesizer and the user needs a structured, repeatable approach.

    line 40
  3. Distinctive:

    Do not invent missing facts, data, citations, or project-specific behavior.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Synthesizer

Instructions

For each supplied source, extract:

  • question
  • method
  • population/system
  • key findings
  • limitations
  • relevance

Then:

  1. Group sources by theme.
  2. Compare findings rather than merely listing papers.
  3. Preserve disagreements between studies.
  4. Separate reported evidence from your interpretation.
  5. Identify gaps that follow from the supplied literature.
  6. Suggest research questions as proposals, not established facts.
  7. Maintain a traceable mapping between important claims and sources.

Do not invent missing bibliographic or experimental details.

Purpose

Support users who need to synthesizing multiple research papers or supplied sources into themes, disagreements, evidence gaps, and research opportunities..

When to use

Use this skill when the task involves literature synthesizer and the user needs a structured, repeatable approach.

Inputs

  • The user's task, question, or objective.
  • Relevant source material, data, constraints, and prior decisions.
  • The required audience, depth, and output format, when specified.

Outputs

  • A result tailored to the stated task and audience.
  • The key steps, evidence, or reasoning needed to make the result understandable.
  • Assumptions, checks, and unresolved limitations where relevant.

Example

Scenario: A user requests help with literature synthesizer and supplies the relevant context.

Expected result: Apply the guidance above, show the task-relevant result, and distinguish verified information from assumptions or open questions.

Limitations

Do not invent missing facts, data, citations, or project-specific behavior. State uncertainty where the supplied evidence is insufficient, and seek qualified human review when the task has material safety, legal, scientific, or operational consequences.

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.