how-to-read-a-paperlisted
Install: claude install-skill thisisrick25/how-to-read-a-paper
# How to Read a Technical Paper
A workflow for reading technical and academic papers efficiently, critically, and with lasting retention. Adapted from Jason Eisner's ["How to Read a Technical Paper"](http://cs.jhu.edu/~jason/advice/how-to-read-a-paper.html) (2009).
## Core Principle
Reading a paper is active work, not passive consumption. You read to *take something away* — understanding, ideas, techniques, or a critical judgment. Invest your time in proportion to why you are reading and what you need to extract.
## The Workflow
### 1. Multi-pass reading
Never read a paper start-to-finish on the first pass.
- **Pass 1 — Skim.** Skip anything that takes mental effort. Get the shape of the paper: where it's going, why it was written, what's old hat vs. new. Use a time budget per page to force momentum.
- **Pass 2 — Read carefully.** Only if the paper still seems worthwhile. Now go deep on the parts that matter (see "Which parts to focus on").
- Optionally follow Keshav's [three-pass method](https://web.stanford.edu/class/ee384m/Handouts/HowtoReadPaper.pdf): each pass has a distinct goal (grasp, grasp content, fully understand).
### 2. Write as you read
Writing keeps attention focused and forces engagement. Produce two kinds of notes.
**Low-level notes** (in-context, on the paper or PDF):
- Restate unclear points in your own words
- Fill in missing details: assumptions, algebraic steps, proofs, pseudocode
- Annotate mathematical objects with their types
- Invent exampl