literature-review-agent

Automate literature discovery and verification with Semantic Scholar for BibTeX-backed paper sections.

32|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/woodfishhhh/EZ_math_model --skill literature-review-agent-woodfishhhh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: literature-review-agent
Source: https://github.com/woodfishhhh/EZ_math_model/tree/main/skills/ez-math-model/external/paper-orchestra/skills/literature-review-agent
Command: npx skills add https://github.com/woodfishhhh/EZ_math_model --skill literature-review-agent-woodfishhhh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-Levenshtein, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It prevents citation inflation and helps produce rigorous Introduction and Related Work sections by collecting, verifying, deduplicating, and then integrating a trusted literature pool with strict citation rules.

Core Features & Use Cases

  • Hybrid discovery + verification: Runs parallel web discovery and then sequential Semantic Scholar verification with fuzzy title matching and temporal cutoffs.
  • Dedup + BibTeX generation: Deduplicates verified papers by Semantic Scholar paperId/DOI/ArXiv and generates a refs.bib file with canonical cite keys.
  • Guardrailed writing with coverage gates: Drafts Introduction and Related Work using only the verified pool and enforces ≥90% pool citation coverage.
  • Use cases: Drafting arXiv/LaTeX paper sections for new projects, rapidly building citation-backed related work, and producing competition-ready literature reviews.

Quick Start

Use the PaperOrchestra coordinator to run Step 3 with your workspace/outline.json and conference_guidelines.md, then verify the generated refs.bib and intro_relwork.tex meet the citation coverage rule.

Frequently Asked Questions about literature-review-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate literature review verification and prevent citation inflation?

Automating literature review verification requires fuzzy title matching and abstract-presence validation against Semantic Scholar, ensuring only deduplicated papers enter the citation pool. This process enforces a strict research cutoff to prevent prior-basis leakage and matches verified papers to structured related-work clusters.

What is the best way to generate BibTeX files and LaTeX related work sections from verified sources?

Generating BibTeX files and LaTeX related work sections from verified sources involves deduplicating papers by paperId or DOI, producing a refs.bib file with canonical cite keys, and drafting template.tex using only the verified pool with a strict citation coverage gate.

How does fuzzy title matching work for Semantic Scholar citation verification?

Fuzzy title matching for Semantic Scholar citation verification uses python-Levenshtein similarity scoring to validate discovered web sources against authoritative database entries. It runs sequential 1 QPS throttled queries with caching to confirm abstract presence before allowing papers into the trusted citation pool.

Can I draft arXiv paper introductions with a strict research cutoff date?

Drafting arXiv paper introductions with a strict research cutoff is supported by enforcing temporal limits during discovery and verification. The system prevents prior-basis leakage by only integrating literature published before the specified cutoff into the Introduction and Related Work sections.

Why does my literature review writing require a 90% citation coverage constraint?

A 90% citation coverage constraint ensures guardrailed writing by forcing the generated Introduction and Related Work sections to cite almost exclusively from the verified, deduplicated literature pool. This prevents citation inflation and maintains rigorous academic standards.

Do I need python-Levenshtein to run semantic scholar literature discovery and deduplication?

python-Levenshtein is required to perform fuzzy title matching during Semantic Scholar verification and deduplication. Without this dependency, the sequential validation process cannot accurately confirm abstract presence or match discovered web papers to canonical database entries.