summary-academic
Skill5 starsChanged 2 months agoMITView on GitHub
Academic paper summarizer for papers, research articles, and scholarly publications. Structured summaries with citations, thesis, conclusions, methodology, implications, and critical analysis. Triggers on "summarize this paper", "summarize this research", "academic summary", "/academic-summary", "quick academic summary", "brief paper summary", and "/academic-summary quick".
In this repository15 other files it gives its agents.
- CLAUDE-template/CLAUDE.mdCLAUDE.md
- ai-council-deepSkill
- ai-councilSkill
- analyze-replySkill
- beamerSkill
- diagram-pdfSkill
- knowledge-baseSkill
- knowledge-base-updateSkill
- narrated-videoSkill
- skill-auditSkill
- skill-buildSkill
- slides-contentSkill
- split-pdfSkill
- summary-generalSkill
- survey-qsfSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 13 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
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 9
Use this skill only for academic papers, research articles, and scholarly publications (peer-reviewed journals, conference proceedings, …
- Distinctive: line 16
TXT attachments: Read the full document before summarizing.
- Distinctive: line 22
Write in an expository style: explain and inform directly without referencing the source material.
- Distinctive: line 25
Use only the explicit section headings specified below.
- Distinctive: line 26
Do not introduce any other section headings, subheadings, or labels.
- Distinctive: line 61
Write one sentence that accurately describes the thesis.
- Distinctive: line 69
Create a detailed bullet-point summary (5-15 bullets):
- Very specific: line 70
Use hyphen and space (- ) for each bullet.
- Very specific: line 82
Use sub-bullets with hyphen and space (- ).
- Distinctive: line 116
Write a concluding paragraph (100-300 words):
- Distinctive: line 118
Use neutral tone with clear, concise language.
- Distinctive: line 120
No flowery language or empty phrases.
- Distinctive: line 135
Before submitting, verify compliance with:
- Distinctive: line 136
All style requirements (expository, no source references).
- Distinctive: line 150
When a quick summary is requested, provide only:
≈ “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
Academic Paper Summary
Use this skill only for academic papers, research articles, and scholarly publications (peer-reviewed journals, conference proceedings, working papers, preprints, dissertations).
For non-academic content (news articles, blog posts, videos, podcasts, general web content), use the summary-general skill instead.
Input Handling
- PDF attachments: Prefer an existing
<basename>_text.mdextract at any size (read the extract, not the PDF). Otherwise check the page count: 4 pages or fewer read the PDF directly; more than 4 pages split with the split-pdf skill into 4-page chunks and read them in a subagent that writesnotes.md, then readnotes.mdas text in the main thread. Reading a long PDF this way keeps the source out of the main context window and avoids shallow comprehension. When this skill is driven by a parent workflow (for example, a slides pipeline) that feeds pre-extracted text, summarize that text directly; the page gate applies only to the standalone PDF path. - TXT attachments: Read the full document before summarizing.
- Web links: Fetch and extract the article content.
- Pasted text: Process directly.
Style Requirements
- Write in an expository style: explain and inform directly without referencing the source material.
- Never use phrases like "the author," "the paper," "the article," or "the study argues."
- Present information as factual statements.
- Use only the explicit section headings specified below.
- Do not introduce any other section headings, subheadings, or labels.
- Take an ideologically neutral position.
- Insert two blank lines between each section.
- Define acronyms on first use as
Term (ACRONYM); bareACRONYMthereafter. First use is the first time the acronym appears anywhere in the summary, not per section. Universally recognized acronyms (US, EU, AI, ML, LLM, CEO, GDP, ROI, R&D, and similar) stay bare. Paper-specific acronyms (for example, RCT, GMM, IV, DID, RLHF) are always expanded on first use.
Length Guidance
| Section | Target Length |
| Key points | 5-15 bullets |
| Conclusions | 1-10 conclusions, 3-6 sub-bullets each |
| Summary paragraph | 100-300 words (scale with complexity) |
| Implications | 3-8 bullets |
Output Format
Structure your response exactly as follows:
1. Citation (no heading)
Provide a citation in Chicago Author-Date style:
Published articles:
Author's Last Name, First Name. Year. *Title of the Article*. Name of the Publication. Date. URL.
Preprints (arXiv, SSRN, bioRxiv, etc.):
Author's Last Name, First Name. Year. *Title of the Article*. Preprint, [Platform Name]. Date. URL.
Working papers:
Author's Last Name, First Name. Year. *Title of the Article*. Working Paper, [Institution]. Date. URL.
"Date" is the full publication date after the publication name (for example, "March 3, 2026" for a specific day, "March 2026" for month-level).
For 3 or more authors, use: First Author's Last Name, First Name, et al. ...
2. Thesis (no heading, no label)
Write one sentence that accurately describes the thesis.
Special cases:
- Literature reviews: State "This is a literature review with no single thesis; it synthesizes research on [topic]."
- Meta-analyses: State the primary research question being analyzed.
- Exploratory studies: State the central research question.
3. Key Points (no heading)
Create a detailed bullet-point summary (5-15 bullets):
- Use hyphen and space (
-) for each bullet. - Include main ideas, themes, and quantitative facts.
- Eliminate unnecessary language.
- Rely exclusively on the provided content.
4. Conclusions:
List 1-10 key conclusions. Under each (3-6 sub-bullets):
- Summarize main ideas and concepts.
- Include evaluation methods.
- Quantify effects with numerical data.
- State implications.
- Include verbatim quotes when helpful.
- Use sub-bullets with hyphen and space (
-).
5. Population:
Describe in paragraph form:
- Population sampled or targeted.
- Research methodology used.
- Time frame covered.
Skip this section entirely (no heading) if not applicable, such as for:
- Theoretical papers.
- Literature reviews without original data collection.
- Purely conceptual or philosophical works.
- Mathematical proofs.
6. Implications:
List real-world applications using bullet points (3-8 bullets, - ).
7. Concepts:
List scientific or economic concepts commonly understood by someone with an undergraduate degree:
- Name each concept.
- Explain it briefly.
- Describe how it relates to the content.
Skip this section entirely (no heading) if no such concepts exist.
8. Issues:
List any:
- Factual errors: State the error and correct information.
- Logical fallacies: Identify type, analyze, and quote relevant text.
- Strong counterarguments: Detail alternative viewpoint and quote relevant text.
Skip this section entirely (no heading) if none exist.
9. Summary (no heading)
Write a concluding paragraph (100-300 words):
- Capture main points and themes.
- Use neutral tone with clear, concise language.
- Simple, straightforward sentence structure.
- No flowery language or empty phrases.
- Scale length with complexity of conclusions.
Output
Save the summary as a markdown file:
- Filename:
<project_name>_summary.md - Location: The project folder (the output directory), never in a subfolder like
TeX/or_build/. - When invoked by a parent workflow (for example, a slides pipeline): follow the parent workflow's placement rules instead.
<project_name> resolves in this order: a name the user specified, otherwise the single source filename without its extension, otherwise the project folder name.
Final Check
Before submitting, verify compliance with:
- All style requirements (expository, no source references).
- Correct section headings only.
- Proper bullet formatting with hyphens.
- Two blank lines between sections.
- Appropriate citation format (published vs. preprint vs. working paper).
- Skipped sections where not applicable.
- Output file placed in the project folder with correct
<project_name>_summary.mdnaming.
Quick Academic Summary Variant
Invoke with: "quick academic summary", "brief paper summary", or /academic-summary quick
When a quick summary is requested, provide only:
- Citation (Chicago Author-Date, same format as above).
- Thesis (one sentence; or state it is a literature review or exploratory study).
- Key Points (5-8 bullets maximum).
- Summary (75-150 words).
Skip the Conclusions, Population, Implications, Concepts, and Issues sections.
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.

