When should you use it?
- You follow several research topics
- New papers arrive faster than you can skim
- You want rigor, not just abstracts
Not for: Systematic reviews that need formal protocols; Paywalled papers you cannot download
What do you need, and what do you get?
You need
- Your subjects and search terms in a small config
- A machine that can run scheduled jobs
- Folders for sources and notes
You get
- A dated file listing fresh papers
- Critical summaries saved beside each PDF
- A record of papers already seen
How does it work, step by step?
- Define topicsList subjects and keywords in a small config file.
- Search on a scheduleQuery arXiv every morning and Scholar weekly, keeping IDs so repeats are skipped.
- Curate by handSkim the digest and save only papers worth deeper reading into matching folders.
- Summarize overnightA second job finds new PDFs and asks the agent for a structured critique.
- Keep sources and notes apartStore the original paper and the generated analysis in separate folders.
The prompt
Our own prompt, inspired by ChatPRD and written to work in Claude Code. Values in lime are placeholders.
Read the PDF at [path]. Return: the core claim; study design and sample; measures and comparison groups; key results with figures and page references; weaknesses and anything that could undermine the result; and relevance to [my topic]. If a number is unclear in the paper, say so instead of estimating. Save as notes/[topic]/[paper-id].md.
Inspired by ChatPRD: How to Automate Academic Research with Claude Code and Python Scripts | AI Workflows. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Scholar search can be rate-limited; keep its cadence slow.
- Summaries can misstate numbers; check effect sizes against the paper before citing.
Our take
The manual selection step in the middle is what makes this research digest work; it keeps volume sane and judgment human. Automating the search and the overnight critique is fine, but deciding which papers deserve a deep read should stay with you. Separating source PDFs from generated notes folders is a smart hygiene habit, because it stops model text being mistaken for the paper later. Ask the summary prompt to quote page numbers for every figure and table so checking claims is quick. Keep the topic list under version control and prune it when interests shift, or the daily file fills with noise. This pattern adapts well to patents, policy papers or court rulings. Check publisher and institutional rules before uploading licensed PDFs to any cloud model, and prefer a local agent when the corpus is sensitive. Skim a sample of critiques weekly for invented numbers; models sometimes fabricate statistics that look plausible next to real ones.
Where the time goes back: Searching and first-pass reading happen on a schedule, so your time goes to choosing and thinking.
FAQ
Does the agent pick the papers?
What does a summary cover?
Source and credit
Inspired by ChatPRD. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- How to Automate Academic Research with Claude Code and Python Scripts | AI Workflows
- Creator
- ChatPRD
- Published on
- chatprd.ai
- Original date
- Jan 19, 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 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 23, 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.