agentleFS
jerry609jerry609/PaperBot/.claude/skills/literature-review/SKILL.md

literature-review

Skill108 starsChanged 8 months agoMITView on GitHub

This skill should be used when the user asks to "do a literature review",

  • Reads credentials

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

8 rules. 0 are common, 0 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    Call paper_search with the research question or topic.

    line 26
  2. Very specific:

    If degraded=True, token-overlap scoring is used (less accurate but functional)

    line 40
  3. Very specific:

    Call paper_summarize for papers recommended as must_read or worth_reading.

    line 54
  4. Very specific:

    If degraded=True, generate a manual summary from the abstract text

    line 58
  5. Very specific:

    Call export_to_obsidian for papers to save as permanent Obsidian notes.

    line 62
  6. Very specific:

    Call save_to_memory with a synthesis of findings across all reviewed papers.

    line 70
  7. Very specific:

    When any LLM-backed tool returns degraded=True:

    line 83
  8. Very specific:

    Use rubric="reproducibility" in paper_judge if the review goal is identifying reproducible papers for implementation

    line 92

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

Conduct a systematic literature review: search, filter by relevance, judge quality, summarize top papers, and save findings to memory.

Workflow

Step 1: Search for papers

Call paper_search with the research question or topic.

  • Parameters: query (required), max_results (default 10; use 20–50 for broad surveys), sources (optional; omit for all sources, or specify ["arxiv", "semantic_scholar"])
  • Returns: list of paper dicts with title, abstract, authors, year, venue, arxiv_id, doi

Step 2: Filter by relevance

For each paper, call relevance_assess with title, abstract, and the same query.

  • Parameters: title, abstract, query, keywords (optional comma-separated terms)
  • Returns: dict with score (0–100) and reason
  • Suggested threshold: discard papers with score below 40
  • If degraded=True, token-overlap scoring is used (less accurate but functional)

Step 3: Judge quality of relevant papers

For papers above the relevance threshold, call paper_judge.

  • Parameters: title, abstract, full_text (optional), rubric (default "default"; pass the research question for context-aware judging)
  • Returns: dimension scores (1–5), overall_score, recommendation (must_read / worth_reading / skim / skip)
  • Prioritize papers with must_read and worth_reading recommendations

Step 4: Summarize top papers

Call paper_summarize for papers recommended as must_read or worth_reading.

  • Parameters: title, abstract
  • Returns: dict with summary key (concise string)
  • If degraded=True, generate a manual summary from the abstract text

Step 5: Export to Obsidian (optional)

Call export_to_obsidian for papers to save as permanent Obsidian notes.

  • Parameters: title, abstract, authors (list), year, venue, arxiv_id, doi (provide whichever identifiers are available)
  • Returns: dict with markdown key — YAML-frontmattered note ready to write to vault

Step 6: Save synthesis to memory

Call save_to_memory with a synthesis of findings across all reviewed papers.

  • Parameters: content (synthesis text), kind ("note" for general observations, "hypothesis" for research directions), user_id (default "default"), scope_type ("global" unless scoping to a specific research track), scope_id (required if scope_type="track"), confidence (0.0–1.0)
  • Returns: dict with created or skipped status

Degraded Mode

paper_judge, paper_summarize, and relevance_assess require a configured LLM API key. paper_search works without LLM and returns raw search results in all cases.

When any LLM-backed tool returns degraded=True:

  • The response also contains an error key describing the issue
  • Set OPENAI_API_KEY or ANTHROPIC_API_KEY and restart the MCP server
  • In degraded mode, proceed with paper_search results only; skip Steps 2–4

Notes

  • For broad surveys (>30 papers), consider running relevance_assess in bulk before paper_judge to reduce LLM calls
  • Use rubric="reproducibility" in paper_judge if the review goal is identifying reproducible papers for implementation
  • The export_to_obsidian step is optional — skip it if the user has not set up an Obsidian vault or does not need persistent notes

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.