literature-review
Skill4 starsChanged 2 months agoMITView on GitHub
Synthesis — use when the user wants to write a literature review section, identify themes and debates across papers, map research gaps, or organize existing papers into a coherent argument. Looks for paper list in paper_search.md; accepts user-supplied reference list if absent.
84 other projects use a version of this.
Adopted by
Most recently taken up by
- delorenj/skillstheir own version, first seen Nov 8, 2026
- DAAF-Contribution-Community/daaftheir own version, first seen Nov 8, 2026
- HughYau/AcademicForgetheir own version, first seen Nov 8, 2026
- BrightGold70/skillstheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- tang1693/yunduan-ai-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use pdf-explore, paper-narrative and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JimLiuSkillpdf-explore
Use this skill when the user has attached a PDF, paper, report, or other document and the answer needs content from more than one place in it: summarize the methods or any other section, compare sections, find where a topic is discussed, read a value or label off a figure or chart, or find/list/extract every instance of something across the whole document (datasets, benchmarks, citations, figures, table rows, accession numbers — including appendices). Skip it only for a single lookup of 1–4 pages quoted in your very next response — `read_file(pages=[...])` attaches pages as images that are dropped from context after one turn, so multi-section answers end up re-reading the same ranges repeatedly. Parses the PDF once in the Python kernel: `pdf_pages` (pages as persistent text), `pdf_outline` (TOC), `pdf_scan` (rank pages by relevance), `pdf_map`/`pdf_extract` (per-page summary / structured fields via parallel haiku calls). For PDF creation/manipulation, use reportlab/pypdf directly.
Also in 9 projects that use this
JimLiuSkillpaper-narrative
Judge and reshape the STORY a paper's figures tell. Input is the work itself — manuscript (or abstract) + figure deck — no hand-written brief. `derive_paper_brief(abstract, captions)` extracts pitch/vision/per-figure-claims; a handling-editor reviewer on the full deck returns hook_verdict (would Fig 1 make me send this for review?), arc (hook→mechanism→evidence→application), figure_moves (panels in the wrong figure), missing_panels (concrete analyses to RUN), kill_list, and boldest_defensible_fig1. Hands per-figure claims to `figure-composer`. Load when writing or revising a paper.
Also in 5 projects that use this
Norman-burySkillbrainstorming-research
Use before writing any paper - clarifies paper type, discipline, topic, methodology, and chapter structure through natural dialogue
Also in 4 projects that use this
lingzhi227Skilllatex-formatting
Handle LaTeX formatting, templates, and styling for academic papers. Set up conference templates (ICML, ICLR, NeurIPS, AAAI, ACL), fix formatting issues, manage packages, and ensure venue-specific compliance. Use when the user needs to set up a paper template, fix LaTeX formatting, or prepare for submission.
Also in 4 projects that use this
lingzhi227Skillnovelty-assessment
Assess research idea novelty through systematic literature search. Multi-round search-evaluate loops with harsh critic persona. Binary novel/not-novel decision with justification. Use before committing to a research direction.
Also in 4 projects that use this
- +6 more from JimLiu
- +1 more from lingzhi227
Other versions84 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 84
- advaitpaliwal/feynman★ 10ksame name
- companion-inc/feynman★ 10ksame name
- getcompanion-ai/feynman★ 10ksame name
- Norman-bury/research-writing-skill★ 3.4ksame name
- Norman-bury/articlewriting-skill★ 3.4ksame name
- HughYau/AcademicForge★ 2.6ksame name
- K-Dense-AI/claude-scientific-writer★ 2.6ksame name
- xuzhougeng/wisp-science★ 1.1ksame name
- wu-yc/LabClaw★ 1.1ksame name
- LeonChaoX/qinyan-academic-skills★ 910same name
74 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- paperpilotSkill
- data-collectorSkill
- integrity-auditorSkill
- paper-searchSkill
- paper-writerSkill
- topic-explorerSkill
- web-accessSkill
The file
Files
Literature Review
职责边界
所需信息:一份文献清单(带摘要/关键词)。
产出:literature/literature_review.md(成文综述,可直接用于论文)。
完成标准:综述按主题组织,覆盖趋势/争议/空白/核心论文四要素,每节末明确本研究的定位,无逐篇罗列。
不做:文献搜索和引用验证(→ paper-search);数据搜集(→ data-collector)。
Step 1 — 收集所需信息
查找顺序:
- 读取
./literature/paper_search.md(paper-search 的产出) - 读取用户在对话中提供的文献列表(BibTeX、手写列表、PDF 目录均可)
- 读取
./topics/research_proposal.md,了解研究问题和理论框架 - 仍无文献清单时,向用户追问:"你有已收集好的文献列表吗?可以粘贴标题列表或上传 .bib 文件。"
向用户确认综述范围:
"文献清单已就绪([N] 篇)。开始写综述前确认:
1. 综述用途:论文中的文献综述节 / 独立综述论文
2. 篇幅要求:[如有]
3. 目标读者对该领域的熟悉程度:[专家 / 一般学术读者]
没有特殊要求的话,按标准结构来。"完成标准:文献清单已加载,研究问题已知,综述用途和篇幅已确认。
Step 2 — 精读与要素提炼
对清单中每篇文献(核心论文精读,其余摘要级别),提炼以下五要素:
| 要素 | 说明 | 追问 |
| 趋势与模式 | 理论、方法或结论随时间的演变 | 某些方法是否越来越流行或被淘汰? |
| 核心主题 | 文献中反复出现的问题或概念 | 哪些概念在不同论文中都被讨论? |
| 争议与矛盾 | 研究者之间的分歧 | 对同一问题有何不同立场? |
| 里程碑论文 | 改变该领域方向的奠基性研究 | 哪篇论文之后该领域发生了明显转向? |
| 空白与不足 | 现有研究缺失的环节或局限性 | 什么问题还没有被回答? |
提炼完成后,向用户展示初步地图:
"文献地图初稿:
主要主题:[X, Y, Z]
核心争议:[...]
识别到的空白:[...]
本研究填补的空白:[...]
你觉得这个地图准确吗?有没有遗漏的重要维度?"完成标准:五要素已覆盖清单中所有核心论文,文献地图已经用户确认。
Step 3 — 规划结构
四种组织方式,可单独使用或组合:
| 结构 | 适用场景 | 注意 |
| 主题式(推荐) | 大多数社科论文 | 每节围绕一个概念/争议,不是一篇论文 |
| 时间顺序 | 追踪理论演进 | 避免变成流水账,每个时期要有判断,解释为什么某个转折点会发生 |
| 方法论 | 方法比较综述 | 明确每种方法的适用条件和局限 |
| 理论流派 | 存在明显学派分野 | 点明流派之间的根本分歧 |
这四种结构可以组合:例如整体按主题划分各节,每节内部按时间顺序讨论该主题的演进。选定结构后说明组合方式。
规划完成后输出大纲让用户确认:
拟定结构:
2.1 [主题A] — 覆盖 [X] 篇
2.2 [主题B] — 覆盖 [Y] 篇
2.3 研究空白与本文定位
确认后开始写作。完成标准:结构已规划,大纲已经用户确认。
Step 4 — 写作
引言
引言完成两件事,顺序固定:
- 说明综述的范围和焦点(覆盖哪些方面,不覆盖什么)
- 预告结构("本综述分三个主题展开……")
不从宏观背景或领域历史开头。
正文各节
按确认的结构逐节撰写,每段写作遵循四条原则:
| 原则 | 做法 | 反面 |
| 综合,不罗列 | 同一段用多篇文献支撑同一论点 | 一篇文献独占一段 |
| 解释,不转述 | 论点后加"这意味着……"或"这说明……" | 只改写摘要内容 |
| 批判性评估 | 必要时指出研究局限(样本、方法、情境) | 只说"该研究发现……" |
| 段落有主题句 | 每段首句说明本段论点,段间用过渡词衔接 | 段落无明确论点,只是素材堆积 |
每节额外要点:
- 开段:说明本节主题和覆盖范围(1句),不用"本节将介绍..."
- 收尾:指出本主题的局限,引向下一节或研究空白
结论
结论完成两件事:
- 总结从文献整体中得出的主要发现——是跨文献的综合判断,不是每篇论文的摘要
- 明确这些发现对本研究的意义:本研究如何填补上述空白,或在此基础上推进
不以"综上所述"开头。以"因此,本研究……"或"基于上述空白……"收尾。
写作全程主动避开 skills/shared/ai-writing-patterns.md 中列出的高频 AI 写作模式。
完成标准:引言/正文/结论三部分均已完成;每段有多篇文献支撑同一论点(无单篇独占段落);每节末有本研究定位的关联;结论有跨文献综合判断,不是逐篇摘要;无 TODO 占位符。
literature_review.md 结构
# 文献综述
## 一、[主题A]
...每段以论点开头,引用支撑论点...
...本主题现有研究的局限:[...]
## 二、[主题B]
...
## 三、研究空白与本文定位
现有研究在以下方面存在不足:
1. [空白1] — 已有研究 [...] 但尚未 [...]
2. [空白2] — ...
本文的贡献在于 [...],与 [对标论文] 的区别在于 [...]。质量 Checklist
- 引言明确了综述范围和结构,未从宏观背景开头
- 按主题组织,每段有多篇文献支撑同一论点(无单篇独占段落)
- 每段有主题句,段间有过渡词
- 有解释和批判性评估,不只是转述
- 五要素(趋势/主题/争议/里程碑/空白)均有体现
- 每节末有本研究定位的关联说明
- 结论有跨文献的综合判断,不是逐篇摘要,以本研究收尾
- 所有引用来自
paper_search.md或用户提供的清单(无新增未验证引用) - 无 AI 套话("综上所述"、"值得注意的是"等)
- 篇幅符合用户要求
完成后的标准输出
✅ 文献综述完成
📄 literature/literature_review.md
结构: [节数] 节
覆盖文献: [N] 篇
识别空白: [X] 个
📊 评价:
[对综述质量的判断,1-2句]
➡️ 建议下一步:
1. paper-writer — 将综述整合进论文正文
2. integrity-auditor — 投稿前验证引用真实性
⚠️ [如有未覆盖的重要文献或结构问题,在此说明]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.

