skills/43-wentorai-research-plugins/skills/literature/metadata/academic-paper-summarizer/SKILL.md
Summarize academic papers with structured extraction of key elements
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research academic-paper-summarizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Academic papers are dense, technical documents that require significant time to read and understand fully. The Academic Paper Summarizer skill provides a systematic framework for extracting the essential elements from research papers into structured, reusable summaries.
This skill is designed for researchers who need to rapidly process large volumes of literature—whether during a systematic review, when onboarding into a new field, or when preparing a literature review section for their own manuscripts. Rather than producing generic summaries, it enforces a structured template that captures the components most relevant to downstream academic work: research questions, methodology, key findings, limitations, and contributions to the field.
The skill works with any academic paper format (PDF, HTML, plain text) and can be adapted across disciplines from biomedical sciences to social sciences, engineering, and humanities. It emphasizes fidelity to the original text while organizing information into a consistent schema that facilitates comparison across papers.
The core of this skill is a multi-section extraction template. When summarizing a paper, populate each of the following fields:
Bibliographic Metadata:
Research Context:
Methodology Summary:
Key Findings:
Critical Assessment:
Relevance and Connections:
When processing multiple papers (e.g., during a literature review), follow this workflow for efficiency:
Example extraction prompt:
Read this paper and extract the following in structured format:
1. Bibliographic info (title, authors, year, journal, DOI)
2. Research question / hypothesis
3. Methodology (design, data, sample, analysis)
4. Key findings (3-5 bullets with effect sizes)
5. Limitations and biases
6. Relevance to [your topic]
7. Key references to follow up
Summaries can be exported in several formats depending on your workflow:
annote field in your BibTeX entrytools
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文(用于「文献综述工具选型」与「一键安装/运行」)。
development
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
documentation
Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.
tools
Guide economists to authoritative data sources with explicit, confirmed data specifications before retrieval; interfaces with Playwright MCP to navigate portals and extract real data, not articles about data.