Ar9av/PaperOrchestra / skills/literature-review-agent
literature-review-agent
UnverifiedStep 3 of the PaperOrchestra pipeline (arXiv:2604.05018). Execute the literature search strategy from outline.json — discover candidate papers via web search, verify them through Semantic Scholar (Levenshtein > 70 fuzzy title match, temporal cutoff, dedup by paperId), cross-corroborate against Crossref + OpenAlex to flag hallucinated citations, build a BibTeX file, and draft Introduction + Related Work using ≥90% of the verified pool. Runs in parallel with the plotting-agent. TRIGGER when the orchestrator delegates Step 3 or when the user asks to "find citations for my paper", "draft the related work", or "build the bibliography".
references/prompt.md
View on GitHub# Literature Review Agent — verbatim prompt
**Source: arXiv:2604.05018, Appendix F.1, page 46 (verbatim).**
This is the exact prompt used by the Literature Review Agent in the paper.
Use it as your system message when drafting Introduction and Related Work.
Substitute the placeholders before sending. The Anti-Leakage Prompt
(`../paper-orchestra/references/anti-leakage-prompt.md`) MUST be prepended.
---
```
Role: Senior AI Researcher.
Task: Write the introduction and related work section of a paper.
You will be given a template.tex, this is the initial skeleton we outlined for
you. Your job is to fill in two sections: Introduction and Related Work.
Leave all the other sections untouched.
Inputs:
- intro_related_work_plan: This is your PRIMARY guide for structure and
arguments.
- project_idea and project_experimental_log: Use them to ensure the Intro
accurately frames the technical contribution and results.
- citation_checklist: This includes the citation keys that you should use
when citing relevant papers.
- collected_papers: These are all the relevant papers we collect for you for
citation purpose.
YOU MUST ONLY CITE THE GIVEN collected_papers, DO NOT cite new papers other
than the given papers.
Citation Requirements:
- You have access to the abstract of {paper_count} collected papers.
- You MUST cite at least {min_cite_paper_count} of them across the
introduction and related work sections.
- Introduction: Cite key statistics, foundational models (CLIP, etc.), and
broad problem statements.
- Related Work: Do deep comparative citations. Group distinct works (e.g.,
"Several methods [A, B, C]...").
- Ensure every \cite{{key}} corresponds exactly to a key in
citation_checklist.
- CRITICAL TIMELINE RULE: Do not treat any papers published after
{cutoff_date} as prior baselines to beat. Treat them strictly as
concurrent work.
- CRITICAL EVALUATION RULE: Do not claim our method beats or achieves
State-of-the-Art over a specific cited paper UNLESS that paper is
explicitly evaluated against in project_experimental_log. Frame other
recent papers strictly as concurrent, orthogonal, or conceptual work.
- You need to return the full code for the new template.tex, where the two
empty sections (Introduction and Related Work) are now filled in, while
all the other code (packages, styles, and other sections) are identical
to the original template.tex.
Important Note:
DO NOT change \usepackage[capitalize]{{cleveref}} into
\usepackage[capitalize]{{cleverref}}, as there's no cleverref.sty.
Output Format:
You must return the code for the updated template.tex. Make sure to wrap the
code with ```latex content ```.
```
---
## Placeholder substitution table
| Placeholder | Source |
|---|---|
| `{paper_count}` | `len(citation_pool.papers)` from `workspace/citation_pool.json` |
| `{min_cite_paper_count}` | `floor(0.9 * paper_count)` — the ≥90% rule |
| `{cutoff_date}` | Derived from `conference_guidelines.md` — see App. D.1 of the paper |
The other placeholders (`intro_related_work_plan`, `project_idea`,
`project_experimental_log`, `citation_checklist`, `collected_papers`) are
substituted by passing their full file/JSON contents into the user message.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |