When should you use it?
- You are writing a thesis or review
- Keyword search keeps missing key papers
- You have a few papers you trust
Not for: Quick background reading; Fields without citation databases
What do you need, and what do you get?
You need
- Three to five seed papers
- Inclusion criteria
- Citation database access
You get
- Expanded paper set with reasons
- Screening log
- Draft review structure
How does it work, step by step?
- Choose seedsPick a few papers you know are central.
- Go backwardCollect papers each seed cites and note why each matters.
- Go forwardFind newer papers that cite the seeds.
- ScreenApply your inclusion criteria and log every exclusion reason.
- IterateRepeat with the strongest new papers as seeds until few new ones appear.
The prompt
Our own prompt, inspired by u/ZS-Portfolio on r/AIToolBench and written to work in Claude Code and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Seed papers: {seeds}. Inclusion criteria: {criteria}. Round 1: list papers cited by each seed and papers that cite each seed. For each give title, year, DOI and a one-line reason it may be relevant. Apply the criteria and log include or exclude with a reason. Suggest which included papers to use as seeds for round 2. Do not summarize findings you have not read.
Inspired by u/ZS-Portfolio on r/AIToolBench: I built a agent skill for academic literature review. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Citation chains drift off topic; keep criteria strict.
- Generated summaries can misstate findings; read the abstracts yourself.
Our take
Citation chasing is how careful researchers have always found the papers keyword searches miss. Packaging it as a skill with scripted steps forces the agent to do the boring, valuable part. The screening log is what makes the result defensible to a supervisor or reviewer. Stop when new rounds return mostly papers you already have; that is a good sign of coverage. Keep the round-by-round logs with your notes so the search can be described in your methods section. Re-run forward citation search near submission so recent work is not missed. Pick a few seed papers you know are central, follow references backward and citing papers forward, and log every exclusion with its reason. Citation chains drift off topic quickly, so keep inclusion criteria strict. Read the abstracts yourself, because generated summaries can misstate findings. Fields without good citation databases will get less from this, and quick background reading does not need the full process.
Where the time goes back: Coverage that used to take days of manual citation tracing comes back as a logged list you can screen.
FAQ
Which tools does it work with?
Why scripted steps?
Source and credit
Inspired by u/ZS-Portfolio on r/AIToolBench. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I built a agent skill for academic literature review
- Creator
- u/ZS-Portfolio on r/AIToolBench
- Published on
- Original date
- Apr 24, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.