agentleFS
tansuasicitansuasici/claude-research-kit/.claude/skills/literature-review/SKILL.md

literature-review

Skill4 starsChanged 6 months agoMITView on GitHub

Synthesize a related-work / literature-review section from the project's OWN library (references.bib + sources/ + vault) — thematic, gap-driven, calibrated, real citations only. Proposes concrete search directions for gaps without fabricating a single source.

92 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pdf-explore, paper-narrative and 10 more.

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.
  • JimLiuSkill

    pdf-explore

    Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.

    Also in 9 projects that use this

  • JimLiuSkill

    paper-narrative

    Judge and reshape the STORY a paper's figures tell. Input is the work itself — manuscript (or abstract) + figure deck — no hand-written brief. `derive_paper_brief(abstract, captions)` extracts pitch/vision/per-figure-claims; a handling-editor reviewer on the full deck returns hook_verdict (would Fig 1 make me send this for review?), arc (hook→mechanism→evidence→application), figure_moves (panels in the wrong figure), missing_panels (concrete analyses to RUN), kill_list, and boldest_defensible_fig1. Hands per-figure claims to `figure-composer`. Load when writing or revising a paper.

    Also in 5 projects that use this

  • Norman-burySkill

    brainstorming-research

    Use before writing any paper - clarifies paper type, discipline, topic, methodology, and chapter structure through natural dialogue

    Also in 4 projects that use this

  • lingzhi227Skill

    latex-formatting

    Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.

    Also in 4 projects that use this

  • lingzhi227Skill

    novelty-assessment

    Assess research idea novelty through systematic literature search. Multi-round search-evaluate loops with harsh critic persona. Binary novel/not-novel decision with justification. Use before committing to a research direction.

    Also in 4 projects that use this

  • +6 more from JimLiu
  • +1 more from lingzhi227

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 3

    Distinctive

    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. Distinctive:

    Before synthesizing anything, take stock:

    line 26
  2. Distinctive:

    If the library is thin for the argument at hand, say so — do not paper over it with invented work.

    line 32
  3. Very specific:

    Read MANUSCRIPT_MAP.md → Thesis / Contribution.

    line 45
  4. Distinctive:

    Write the section in LaTeX:

    line 49
  5. Very specific:

    Every non-trivial claim carries a real \cite{key} resolving in references.bib.

    line 51

“Common” is measured: kept by at least 6 in 10 of the 72 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

Literature Review

Core Rule

Synthesize only what is in the library. Never invent a citation, author, year, finding, or quantity. A literature review's deadliest failure is the model confidently asserting "prior work shows X \cite{plausible2021}" for a paper that does not exist. This skill works your references.bib + sources/ (+ vault/ if present) and nothing else. For what the library lacks, it emits search directions — what to look for — never a fabricated source to fill the hole.

When to Use

Invoke with /literature-review when:

  • Drafting or revising the Related Work / Background section
  • Grounding the Introduction's gap claim in real prior work
  • Positioning your contribution against the field before submission
  • Checking whether your library actually covers the themes your argument needs

Process

Phase 1 — Inventory the library

Before synthesizing anything, take stock:

  • Count references.bib entries; note which have full text or notes in sources/ (or a summary in vault/).
  • Flag metadata-only entries — you have the citation but not the content. You may cite their existence but must not assert specific findings without the source.
  • Report coverage: N references / M with readable source / K metadata-only.

If the library is thin for the argument at hand, say so — do not paper over it with invented work. A 4-source "review" is a 4-source review.

Phase 2 — Cluster thematically

A literature review is an argument, not an annotated list ("Smith said X. Jones said Y."). Group the real sources by theme / method / finding / chronology and build a map. Example clusters for an LLM-agent paper:

  1. Tool-augmented agent frameworks
  2. Hallucination & faithfulness in LLM outputs
  3. Verification / self-correction methods
  4. Agent evaluation benchmarks

Phase 3 — Gap analysis (against the thesis)

Read MANUSCRIPT_MAP.md → Thesis / Contribution. Locate the gap the synthesis must set up: "the literature establishes A and B but not C, which is our contribution." Every theme should pull toward that gap. If a cluster does not serve the thesis, it is background, not related work.

Phase 4 — Draft the synthesis

Write the section in LaTeX:

  • Every non-trivial claim carries a real \cite{key} resolving in references.bib.
  • Calibrated verbs — \citet{ex2023b} reports / finds / observes, not proves. Match the verb to what the source licenses (see agent_docs/academic-style.md).
  • One paragraph per theme, each ending by advancing toward the gap.
  • Metadata-only claims get a [verify: source not read] marker, never a confident assertion.

Tool-augmented agents reliably decompose multi-step tasks \citep{ex2023a}, yet their tool calls remain error-prone under distribution shift \citep{ex2023b}. Proposed remedies emphasise post-hoc self-correction \citep{ex2024c}; deterministic pre-execution gating remains unexplored.

Phase 5 — Coverage + search-direction report

For every theme that is thin or missing, emit concrete search directions — what to look for, not a fabricated paper:

  • Keywords / queries to run (e.g. "constrained decoding tool use", "self-consistency verification agents").
  • Venues & years likely to hold it (e.g. NeurIPS / ICLR / ACL 2023–2025).
  • Citation chaining — follow the references/citations of a paper you already have (e.g. "backward-cite from \cite{ex2023b}").
  • Author follow-ups — later work by an author already in your library.

The loop stays honest: you fetch the result → ingest it (/lit-ingest if the vault module is installed, or add to references.bib + sources/) → re-run /literature-review. The skill never closes a gap by inventing a source.

Phase 6 — Verify

  • citation-gate.sh confirms every \cite resolves (run an edit, or check .hook-state/last_quality_gate.json).
  • Spawn the fact-checker agent on the load-bearing claims to confirm the source supports the verb.
  • Report the tally: (synthesized from read sources / metadata-only / gaps with search directions).

Output Format

  1. The drafted section — LaTeX, real citations, calibrated, gap-directed.
  2. Coverage table — theme → # sources → read vs metadata-only → strength.
  3. Search directions — per thin/missing theme, the concrete leads above (no fabricated papers).
  4. Tally — (synthesized / metadata-only / gaps).

Pairs With

  • vault/ + /lit-ingest (E1) — the ideal backing store; ingest fetched sources here, then re-run.
  • fact-checker agent — verifies the synthesis against sources.
  • citation-gate.sh — guarantees no dangling \cite.
  • /gap-finder — surfaces uncited/unsupported claims in the draft.
  • /claim-check — claim-by-claim audit once the section is written.

Common Rationalizations (all rejected)

  • "I'm fairly sure there's a paper on X." → Emit a search direction, not a \cite. Confidence is not a citation.
  • "The library is thin, I'll round it out with well-known work." → No. Report the gap with search directions; let the author fetch real sources.
  • "This source probably says X." → If you have not read it (metadata-only), mark [verify]; do not assert the finding.
  • "A review needs ~40 references, so I'll list plausible ones." → A review needs the references you actually have; the gap report tells you how to get the rest.

Notes

  • Two modes: vault-backed (rich synthesis from vault/ summaries + concepts) and bib+sources-backed (works references.bib + sources/ notes; more metadata-only flags).
  • This skill drafts and reports; changing the contribution framing is a Protected Claim — confirm with the author.
  • Reasoner-tier work (synthesis across many sources) — see CLAUDE.md → Model Selection.

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.