When should you use it?
- You review many papers for research or study
- Pasting them one by one eats whole days
- You can keep files in a local folder
Not for: Trusting relevance scores without reading the top papers; Citing summaries you have not verified
What do you need, and what do you get?
You need
- Your papers gathered in one directory
- A context file describing your research theme
- A saved command for the review flow
You get
- The aim, method and findings pulled from each paper
- A relevance-scored, ranked reading list
- A citation-overlap view of core papers
How does it work, step by step?
- Collect papers in one folderPut the PDFs where the agent can read them all at once.
- Write down your themeRecord your research topic and keywords in a context file it reads every run.
- Save the review as a commandMake a reusable command so you do not re-type the instructions.
- Run it over the folderHave it extract key points and score each paper's relevance to your theme.
- Find the core literatureAsk it to identify papers cited across many others as must-reads.
The prompt
Our own prompt, inspired by Claude Code研究所 and written to work in Claude Code. Values in lime are placeholders.
Work through every PDF sitting in the papers/ folder. For each, pull the research aim, method, key findings and keywords. Using my research theme and keywords in [context file], score each paper's relevance as high, medium or low and output a ranked reading list as Markdown. Then identify the papers cited across the most others as likely core literature. Save the result to a file.
Inspired by Claude Code研究所: When Researchers and Graduate Students Use Claude Code: How Processing Entire Folders of Dozens of Papers Dramatically Changed Literature Reviews|Claude Code研究所. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Scores guide reading; they do not replace it, so read the high-relevance papers yourself.
- Keep your theme file current, since stale context skews every relevance call.
Our take
The real gain described by Claude Code研究所 is working at folder level with a persistent context file, which a browser chatbot cannot do. Once your research theme is written down, every paper is judged against the same criteria, and saving the review as a command means next month's batch takes one line. The citation-network idea, finding papers that many others in the folder reference, is a quick way to spot core literature you may have missed. Treat every score as a reading map, not a verdict. Models summarize abstracts well but can misstate methods, sample sizes or effect directions, and a relevance score reflects how the paper matches your wording rather than its importance. Read the top-ranked papers properly before citing them, and spot-check a few low-ranked ones to see whether anything valuable is being buried. Keep the extracted summaries in files next to the PDFs, so errors can be corrected once. Check your publisher and institution rules on uploading licensed papers to AI services, and keep scheduled collection of new papers to sources you trust.
Where the time goes back: Literature reviews that swallow multiple days shrink to half an hour, so you spend time on the research instead of the triage.
FAQ
Why not a chatbot?
How much time does it save?
Source and credit
Inspired by Claude Code研究所. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- When Researchers and Graduate Students Use Claude Code: How Processing Entire Folders of Dozens of Papers Dramatically Changed Literature Reviews|Claude Code研究所
- Creator
- Claude Code研究所
- Published on
- note.com
- Original date
- Jul 27, 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.