← Back to library

Write paper summaries from your annotations into Zotero

Pin Shuai, a hydrology researcher, pairs Claude with his local Zotero library so searches stay inside papers he already owns. After reading, he has it turn color-coded highlights into notes on results and open questions, then files those notes back into Zotero.

  • OutcomeGet a short note of main results and open gaps for each paper you have read, saved inside your reference manager.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditPin Shuai
View original
Works with
ClaudeClaude Code

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

When should you use it?

  • You annotate papers but rarely write summaries
  • You keep references in Zotero
  • You worry about invented citations

Not for: Papers you have not read; Writing your own critical analysis

What do you need, and what do you get?

You need

  • Zotero library with annotated papers
  • Connector between Claude and Zotero

You get

  • Summary note per paper with findings and gaps

How does it work, step by step?

  1. Connect your libraryLink the assistant to Zotero so it searches only what you own.
  2. Annotate as usualKeep your color code so annotation types are distinguishable.
  3. Ask for the noteAsk for a summary built from your highlights.
  4. Answer its questionsIt may ask what the note should emphasize.
  5. Check in ZoteroOpen the note and edit anything you disagree with.

The prompt

Our own prompt, inspired by Pin Shuai and written to work in Claude and Claude Code. Values in lime are placeholders.

Prompt0 variables
Using my Zotero library, find [author, year]. Based only on my annotations on that paper, write a note with: the research question, three key findings, the main knowledge gaps the authors or I flagged, and one line on methods. Ask me one question first if the annotations conflict. Save it as a child note on the item and do not modify anything else.

Inspired by Pin Shuai: Academic Use Cases with Claude | Shuai Computational and Integrated Hydrology Group. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Summaries reflect your highlights; unannotated sections are missed.
  • Keep your own critique separate from the generated summary.

Our take

Grounding the assistant in your own library is the simplest fix for fabricated citations, and the annotation-first approach keeps your judgment in the loop. Limiting searches to papers already in your library means every reference the assistant mentions is one you can open, which removes the usual worry about invented citations. Building notes from your own color-coded highlights keeps the summary tied to what you judged important while reading. That cuts both ways: sections you did not annotate will not appear, so a thin highlight pass produces a thin note. Keep the color code consistent so the assistant can tell results from questions. Answer its questions about emphasis honestly rather than accepting the default. Open each note in Zotero and edit anything you disagree with, and keep your own critique in a separate note so the generated summary never passes as your analysis. This only suits papers you have actually read.

Where the time goes back: The summary you meant to write after every paper happens in a minute.

FAQ

Why go through Zotero?
Answers come from papers you hold, which stops made-up references.
Does it replace reading?
No. It summarizes your annotations after you have read.

Source and credit

Inspired by Pin Shuai. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Academic Use Cases with Claude | Shuai Computational and Integrated Hydrology Group
Creator
Pin Shuai
Published on
groundwater.usu.edu
Original date
Apr 23, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude
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 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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

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 & AdminSkill✓ AI dry run

Compare design options with a weighted score and stress test

Use the trade-study-report skill from Anthropic's Claude for Manufacturing plugin to turn a filled-in options matrix and test results into a ranked, sourced comparison, set aside any option that breaks a hard requirement, vary the weights to see whether the winner changes, and draft a decision memo an engineer reviews and signs.

Credit: anthropics

Under an hour
Operations & AdminSkill✓ AI dry run

Connect your agent to a system with no ready connector

Use the custom-connector skill from Anthropic's Claude for Manufacturing plugin to name the exact system and one data flow, check for an existing vendor or community MCP server before building anything, settle on the highest workable access route down to a scheduled export, record why, keep credentials out of the chat and explain how the chosen route is likely to break.

Credit: anthropics

An afternoon+
Operations & AdminSkill✓ AI dry run

Query a Canvas LMS course through a chat tool

Answer course questions like who has not submitted or how grades are spread without clicking through LMS menus.

Credit: Vishal Sachdev

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Turn course evaluations into a tracked list of fixes

Make student feedback lead to real course changes by turning its themes into a checklist issue that agents work through and you tick off.

Credit: Nick Feamster

An afternoon+