paper-reading
Skill1 starsChanged 6 days agoMITView on GitHub
Read a research paper the way a researcher does before explaining it, and write down what an explainer needs - the method in execution order, every tensor and size, every number with its table or figure, what was released, and what the paper leaves undefined. Use before planning any explainer video, figure or summary of a paper, or when asked to read, digest or extract a paper.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- unravel11/research-paper-skillstheir own version, first seen Nov 16, 2026
- crce-ux/paper-readingtheir own version, first seen Nov 8, 2026
- paratrooper-vincent/paper-readingtheir own version, first seen Nov 1, 2026
- xiaofengShi/paper-reading-skilltheir own version, first seen Oct 26, 2026
- jinxiy1104/Obsidian_Paper_Ingestion_Skilltheir own version, first seen Oct 20, 2026
- BH2-4/paper-craft-pipelinetheir own version, first seen Oct 20, 2026
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- voidful/academic-skills★ 126same name
- jxtse/scientific-research-skills★ 68same name
- Immortalqx/my_codex_skills★ 54same name
- Agentchengfeng/paper-reading-skills★ 28same name
- Kingslayer-bot/paper-reading-skill★ 28same name
- a1henu/paper-reading-skill★ 11same name
- xiaofengShi/paper-reading-skill★ 10same name
- Shen-An/learn-skill★ 5same name
- techdou/paper-reading★ 5same name
- JinukMoon/agent-skills★ 4same name
12 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 repositoryOne other file it gives its agents.
- truetakeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Read the whole paper three times, each time for something different.
- Distinctive: line 22
How it works, in the order the code runs: Read the method section with the framework figure open.
- Distinctive: line 64
Find what was released: before planning: repository, licence, weights, data, and what is *not* there.
- Very specific: line 76
When the reading is done, tell the user the claim, the modules in order, the gaps and their assumptions, and what was and was not released, …
“Common” is measured: kept by at least 6 in 10 of the 12 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
Reading a paper before explaining it
An explainer is only as true as the reading behind it. This skill turns a paper into paper.json and a short
method.md, which every later step (scene plan, captions, numbers on screen) cites. Nothing goes on screen that
cannot be traced to a line in one of them.
The three passes
Read the whole paper three times, each time for something different. Do not skip to the method.
- What it claims (10 minutes). Title, abstract, introduction's contribution list, every figure and its caption, conclusion. Write the claim in one sentence, the problem in one sentence, and the contributions as a list. Note which contribution is the method (what a reader could re-implement) and which are data or benchmarks.
- How it works, in the order the code runs. Read the method section with the framework figure open. Write the
modules in execution order: for each, its input, its output, its size at each step, and the equation or
algorithm that defines it. Follow one sample through; if the paper never says a size, compute it from the
architecture and mark it
derived. - The details a re-implementer would trip on. Hyperparameters (with the sentence that states them), thresholds, training versus inference differences, pre- and post-processing (resize, normalisation, NMS), every number in the tables you may show, and every place the paper is silent.
Tables and figures are often images in the PDF: render the page (pdftoppm -r 200) and read them; never guess a
number from text that did not extract.
What to write
paper.json, in this shape (keys may be empty, never invented):
{
"paper": {"title": "", "authors": [], "venue": "", "year": 0, "doi": "", "arxiv": "", "license": ""},
"claim": "", "problem": "",
"contributions": [{"kind": "method|data|benchmark|analysis", "text": ""}],
"modules": [{"name": "", "order": 1, "input": "", "output": "", "sizes": [""], "defined_by": "Eq. 3 / Alg. 1 / Sec. III-B",
"parallel_with": []}],
"equations": [{"id": "Eq. 1", "tex": "", "symbols": {"x": "meaning"}, "where": "Sec."}],
"hyperparameters": [{"name": "", "value": "", "quote": "", "where": ""}],
"numbers": [{"value": "", "meaning": "", "where": "Table III, row SiamFC, column noDET"}],
"released": {"code": "", "weights": "", "data": "", "licenses": ""},
"gaps": [{"what": "", "why_it_matters": "", "our_assumption": ""}],
"figures_to_redraw": [{"figure": "Fig. 7", "why": "", "license_note": ""}]
}method.md: the method in plain words, one short paragraph per module, in execution order, each ending with the
source it came from. This is what a reviewer (the paper's own field) reads to check the explainer.
Rules
- Quote, do not paraphrase, every hyperparameter and threshold, with its section. "τt and τd are set to 0.9" beats "high thresholds".
- Every number carries its location: table, row, column; or figure and axis. Numbers measured by us are never presented as the paper's, and the paper's are never presented as ours.
- Separate the paper's method from what it uses. A tracking paper that plugs in Faster R-CNN does not own Faster R-CNN; say which parts are the contribution.
- Find what was released before planning: repository, licence, weights, data, and what is not there. A video that needs the authors' weights cannot be made from a paper that did not release them; plan with what exists and label substitutes.
- List the gaps. Anything undefined that an explainer must decide (a score's normalisation, an unstated input
size) goes in
gapswith the assumption chosen. The explainer states that assumption on screen. - Licences of the paper itself: the publisher's version is usually all rights reserved; the arXiv version may carry a Creative Commons licence. Redraw figures from your own real data either way, and cite the original.
- Cross-check against code wherever code exists (sign conventions, transposes, inverse matrices, the order of steps), and record what was checked.
Hand-off
When the reading is done, tell the user the claim, the modules in order, the gaps and their assumptions, and what
was and was not released, in a few lines. The explainer plan starts from paper.json, not from the PDF.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

