paper-reader
Skill5 starsChanged 4 months agoMITView on GitHub
Read one paper (PDF, arXiv id, DOI, or text) and produce a structured note: the claim, method, evidence, limitations, how it relates to the student's research question, and quotable passages with locations, so that lit-review-synthesis can build an argument from many notes. Use when working through a reading list, when a supervisor asks what a paper actually shows, or before citing a paper for a specific claim.
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Read the paper, not the abstract.
- Very specific: line 25
Write one markdown file per paper under research/notes/, named <firstauthor><year>-<short-title>.md, with the BibTeX key in the front …
- Distinctive: line 71
Never invent a page number.
- Very specific: line 73
When reading several papers, do not compare them here.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read the paper, not the abstract. The note you produce will be trusted later, when the student is writing under deadline and will not reopen the PDF, so every claim in the note must be traceable to a page or section.
Get the text
- A local PDF: extract text (
pdftotext -layout file.pdf -), and read the figures and tables where the text is unclear. - An arXiv id: fetch the LaTeX source when available (
https://arxiv.org/e-print/<id>, a gzipped tar) because it keeps equations and tables intact; otherwise the PDF (https://arxiv.org/pdf/<id>). - A DOI: resolve it to metadata with CrossRef, then ask the student for the PDF if it is not open access. Do not summarise a paper from its abstract and pretend it was read.
Read in this order
- Abstract, introduction, conclusion: what the authors claim.
- Method and setup: what they did, precisely enough to judge the claim.
- Results, including tables: what the evidence shows, including what it does not show.
- Related work and limitations: where they place themselves and what they concede.
- References: which works they lean on (candidates for
citation-graph).
The note
Write one markdown file per paper under research/notes/, named <firstauthor><year>-<short-title>.md, with the BibTeX key in the front matter so citation-verifier and lit-review-synthesis can join them:
---
key: smith2023feedback
title: ...
authors: ...
year: 2023
venue: ...
doi: 10.xxxx/yyyy
type: empirical | design | survey | theory | position
read: 2026-09-21
relevance: high | medium | low
---
## One-sentence claim
What the paper says it shows, in your words.
## Research question it answers
Their question, and which of the student's sub-questions it bears on.
## Method
Design, data (source, size), procedure, metrics, baselines. Enough to judge validity.
## Evidence
The key results with numbers, and the table or figure each comes from (Table 3, Fig. 2).
What was not tested.
## Limitations
Theirs (from the paper) and yours (what you noticed).
## Relation to this thesis
Supports / contradicts / extends / provides method for: which claim of the student's, and how.
## Quotable
> "exact sentence" (p. 4, Sec. 3.2)
At most five. Exact text, with location, for use in the review.
## Follow-up
References worth chasing, with the reason.Rules
- Distinguish what the paper claims from what its evidence supports; when they differ, say so in Limitations.
- Numbers are copied, not rounded or recalled. If a number is unreadable in the extraction, write
[unreadable, check Table N]. - Never invent a page number. If the source is LaTeX or HTML with no pagination, cite the section.
- The note is in the student's voice for the student's purpose; "relevance: low" is a valid and useful outcome.
- When reading several papers, do not compare them here; that is
lit-review-synthesis. One paper, one note.
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- huangkiki/dailypaper-skills★ 1.3ksame name
- Ethan2409/PaperFlow★ 12same name
- TengleWang/PaperFlow★ 12same name
- Hongyuan-Lu/paper-reader★ 5same name
- CHB-learner/scholarflow-claude-skills★ 4same name
- WbleJ/Paper-reader★ 3same name
- jacquardlabs/study-skills★ 2same name
- pym96/skills★ 2same name
- chycycc/paper-reader★ 1same name
- OU-GC/Practical-Claude-Code-Skills-for-Chinese-speaking-Masters-Students★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository89 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- improveSkill
- academic-writingSkill
- benchmark-reportingSkill
- bibtex-managerSkill
- citation-graphSkill
- citation-verifierSkill
- design-science-methodologySkill
- docx-thesisSkill
- experiment-reproducibilitySkill
- latex-toolkitSkill
- literature-searchSkill
- lit-review-synthesisSkill
- proofread-academicSkill
- research-figuresSkill
- research-methodologySkill
- research-questionSkill
- statistics-advisorSkill
- supervisor-updateSkill
- systematic-reviewSkill
- thesis-proposalSkill
- coolify-image-appSkill
- coolify-vps-baselineSkill
- deploy-verificationSkill
- express-prisma-coolify-imageSkill
- ghcr-coolify-pipelineSkill
- live-domain-cutoverSkill
- nextjs-coolify-imageSkill
- proxy-client-addressSkill
- vps-ops-toolkitSkill
- adr-writingSkill
- openapi-specSkill
- readme-writingSkill
- technical-writingSkill
- adversarial-reviewerSkill
- api-design-reviewSkill
- code-review-responseSkill
- create-agentSkill
- create-commandSkill
- create-hookSkill
- create-skillSkill
- db-migration-safetySkill
- dependency-upgradeSkill
- dockerfile-best-practicesSkill
- error-handling-patternsSkill
- executing-plansSkill
- explain-codebaseSkill
- fix-ciSkill
- github-actions-pipelineSkill
- grill-with-docsSkill
- incident-postmortemSkill
- logging-and-observabilitySkill
- parallel-agentsSkill
- performance-optimizationSkill
- refactoring-recipesSkill
- solid-principlesSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

