paper-reading
Skill68 starsChanged 7 months agoMITView on GitHub
Reads and analyzes academic papers (arXiv preprints, conference / journal PDFs, Zotero items) at three configurable depths: quick skim (2 min), standard read (10 min), or deep analysis (30 min). Produces structured digests covering problem, method, key innovation, results, limitations, reproducibility, hidden assumptions, and connections to the user's other work. Use when the user shares an arXiv link, PDF, or paper title and asks to read / summarize / digest / TL;DR / analyze / review / critique / explain / break down a paper, asks about a paper's contributions / methods / results / equations / figures, wants to compare two papers side by side, or needs a reading note for their records.
20 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- techdou/paper-readingtheir own version, first seen Oct 20, 2026
Other versions20 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 20
- voidful/academic-skills★ 126same 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
- luffysolution-svg/omnischolar★ 4same name
10 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 repository6 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 76
Follow the appropriate level template above.
- Distinctive: line 80
After reading, save the digest:
- Distinctive: line 82
If user confirms, add/update Zotero entry with notes
- Distinctive: line 94
Check the ablation study — it reveals what actually matters in their method
- Distinctive: line 95
Read the limitations/future work section — often more honest than the intro
- Distinctive: line 96
Look at Appendix — important details are often buried there
- Distinctive: line 104
Check if baselines are fairly implemented (same hyperparameter search budget?)
- Distinctive: line 105
Look for cherry-picked examples in qualitative analysis
- Distinctive: line 109
When user asks to compare two papers:
“Common” is measured: kept by at least 6 in 10 of the 10 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
Paper Reading
Structured workflow for reading academic papers efficiently.
When to Use
- User shares an arXiv link or PDF and asks to read/summarize it
- User asks about a specific paper's contributions, methods, or results
- User wants a reading digest for their records
- User asks to compare a paper against related work
Reading Levels
Level 1: Quick Skim (2 min)
When: User just wants to know if a paper is worth reading
Output:
- Paper title, authors, venue, year
- One-paragraph summary (what problem, what method, what result)
- Key contribution in one sentence
- Relevance assessment to user's work
- Recommendation: Read / Skip / Skim only
Level 2: Standard Read (10 min)
When: User wants to understand the paper's approach
Output:
- Problem: What gap does this address?
- Method: How do they solve it? (with key technical details)
- Key innovation: What's genuinely new vs. incremental?
- Results: Main numbers + comparison to baselines
- Limitations: What they don't do, acknowledged or not
- Connections: How does this relate to user's active projects?
Level 3: Deep Analysis (30 min)
When: User is seriously considering building on this paper
Output:
- Everything from Level 2, plus:
- Detailed methodology: Step-by-step technical walkthrough
- Reproducibility assessment: Can you implement this from the paper alone?
- Experimental design critique: Are the baselines fair? Metrics appropriate?
- Hidden assumptions: What are they not saying?
- Extension opportunities: How could this be improved or adapted?
- Key equations/algorithms: Extracted and explained
- Figure analysis: What do the key figures actually show?
Workflow
Step 1: Obtain Paper
arXiv link → Download PDF, extract text
PDF file → Extract text directly
Paper title → Search Semantic Scholar → get arXiv link → download
Zotero item → Get from local libraryStep 2: Read at Requested Level
Follow the appropriate level template above. When in doubt, start with Level 2.
Step 3: Store Digest
After reading, save the digest:
- Store structured summary to local dashboard
- If user confirms, add/update Zotero entry with notes
Step 4: Connect to Context
- Link to user's active projects if relevant
- Suggest follow-up papers (from references or "cited by")
- Note if this paper supports or contradicts prior reads
Reading Heuristics
For ML/AI papers:
- Jump to Table 1 (main results) first — if the numbers aren't impressive, calibrate expectations
- Check the ablation study — it reveals what actually matters in their method
- Read the limitations/future work section — often more honest than the intro
- Look at Appendix — important details are often buried there
For methods papers:
- Focus on Figure 1 (method overview) + Section 3 (method) + Table 1 (results)
- Skip related work on first pass — come back only if you need positioning context
For empirical papers:
- Focus on experimental setup, metrics, and statistical significance
- Check if baselines are fairly implemented (same hyperparameter search budget?)
- Look for cherry-picked examples in qualitative analysis
Paper Comparison Mode
When user asks to compare two papers:
| Aspect | Paper A | Paper B |
|--------------|------------------|------------------|
| Problem | | |
| Method | | |
| Data | | |
| Key metric | | |
| Advantage | | |
| Limitation | | |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.

