paper-summarization
Skill1 starsChanged 51 days agoMITView on GitHub
Summarize a research paper or long report into two Markdown files: a section-by-section reading guide and an analytical synthesis organized around its central ideas.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- samuelhe52/skillsword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- samuelhe52/skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository5 other files it gives its agents.
- experiment-infra-designSkill
- html-slidesSkill
- paper-walkthrough-slidesSkill
- remote-gpu-experimentsSkill
- test-value-auditSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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 8
Create two complementary artifacts from the paper or report:
- Distinctive: line 13
Avoid imposing a fixed analytical template: an empirical paper, a theoretical argument, a survey, and an engineering report call for …
- Very specific: line 15
Use the user's requested location and names, or established project conventions.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paper Summarization
Create two complementary artifacts from the paper or report:
reading-guide.md: A two-level outline following the source's sections and immediate subsections, with a short summary paragraph for each item.analytical-synthesis.md: An independent organization of the material that explains its central ideas, how they fit together, and what the reader should take away. Choose the structure and depth to suit the source and the user's interests. Give more attention to what matters; connect ideas across sections and assess the support for consequential claims where useful. Keep the authors' claims distinguishable from your interpretation.
Avoid imposing a fixed analytical template: an empirical paper, a theoretical argument, a survey, and an engineering report call for different treatments. Include source pointers where they help the reader return to important passages or evidence.
Use the user's requested location and names, or established project conventions. Otherwise, save both files under paper-summaries/<paper-slug>/ in the current working directory. Identify and link the source in each artifact, and link both completed files in the handoff.
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.