← Back to library

Scan new preprints daily and critique the ones you keep

ChatPRD describes a researcher on How I AI who runs two scheduled scripts. One queries arXiv daily and Scholar weekly from a topic list, skips anything already seen and writes fresh hits to a dated Markdown file. Worth keeping PDFs go into topic folders; a nightly job then has Claude Code critique design, numbered results and weaknesses.

  • OutcomeReceive a dated digest of new papers on your topics each morning, then find structured critical summaries of the PDFs you chose waiting the next day.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditChatPRD
View original
Works with
Claude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

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?

  1. Define topicsList subjects and keywords in a small config file.
  2. Search on a scheduleQuery arXiv every morning and Scholar weekly, keeping IDs so repeats are skipped.
  3. Curate by handSkim the digest and save only papers worth deeper reading into matching folders.
  4. Summarize overnightA second job finds new PDFs and asks the agent for a structured critique.
  5. 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.

Prompt0 variables
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?
No. She manually selects which PDFs get analyzed.
What does a summary cover?
Core claim, design and sample, measures, findings with numbers, limitations and relevance to the topic.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Ask Reddit's experience before you pick a library

Let your coding agent search Reddit for long-term user reports on a library, an error message or a competitor before you commit to a choice.

Credit: u/karanb192 on r/ClaudeCode

Minutes
Operations & AdminWorkflow✓ AI dry run

Build a paper's data pipeline with a coding agent

Hand the collection, cleaning and charting code for a research project to an agent while you review it in your editor and notebooks.

Credit: Kevin Yang

Under an hour
Operations & AdminWorkflow✓ AI dry run

Get agent-written browser tests that survive CI

Get a Playwright test written by Claude Code against your running app, reviewed twice, repeated to catch flakiness and committed beside its plain-English scenario.

Credit: Jakob Norlin

Under an hour