跳到主要内容

academic-paper-review 精选

Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation. Trigger on queries involving paper URLs, uploaded PDFs, arXiv links, or requests like "review this paper", "analyze this research", "summarize this study", or "write a peer review".

在 GitHub 打开

安装方式

cp -r skills/public/academic-paper-review ~/.claude/skills/academic-paper-review

把该 skill 目录放进客户端 skills 目录。不同客户端的目录可能不同,Claude Code 默认是 ~/.claude/skills/

整仓一次性获取:git clone --depth 1 https://github.com/bytedance/deer-flow.git

依赖与权限

  • 无需 API Key
  • 无需联网
  • 无外部命令依赖
  • 以上为按正文与 frontmatter 自动推断的信号,仅供参考;安装前建议先阅读原文。
触发场景
analyzecritiqueresearch art

SKILL.md 正文

来源 bytedance/deer-flow@b346b17 · 许可 MIT · 内容未修改

Academic Paper Review Skill

Overview

This skill produces structured, peer-review-quality analyses of academic papers and research publications. It follows established academic review standards used by top-tier venues (NeurIPS, ICML, ACL, Nature, IEEE) to provide rigorous, constructive, and balanced assessments.

The review covers summary, strengths, weaknesses, methodology assessment, contribution evaluation, literature positioning, and actionable recommendations — all grounded in evidence from the paper itself.

Core Capabilities

  • Parse and comprehend academic papers from uploaded PDFs or fetched URLs
  • Generate structured reviews following top-venue review templates
  • Assess methodology rigor (experimental design, statistical validity, reproducibility)
  • Evaluate novelty and significance of contributions
  • Position the work within the broader research landscape via targeted literature search
  • Identify limitations, gaps, and potential improvements
  • Produce both detailed review and concise executive summary formats
  • Support papers in any scientific domain (CS, biology, physics, social sciences, etc.)

When to Use This Skill

Always load this skill when:

  • User provides a paper URL (arXiv, DOI, conference proceedings, journal link)
  • User uploads a PDF of a research paper or preprint
  • User asks to "review", "analyze", "critique", "assess", or "summarize" a research paper
  • User wants to understand the strengths and weaknesses of a study
  • User requests a peer-review-style evaluation of academic work
  • User asks for help preparing a review for a conference or journal submission

Review Methodology

Phase 1: Paper Comprehension

Thoroughly read and understand the paper before forming any judgments.

Step 1.1: Identify Paper Metadata

Extract and record:

FieldDescription
TitleFull paper title
AuthorsAuthor list and affiliations
Venue / StatusPublication venue, preprint server, or submission status
YearPublication or submission year
DomainResearch field and subfield
Paper TypeEmpirical, theoretical, survey, position paper, systems paper, etc.

Step 1.2: Deep Reading Pass

Read the paper systematically:

  1. Abstract & Introduction — Identify the claimed contributions and motivation
  2. Related Work — Note how authors position their work relative to prior art
  3. Methodology — Understand the proposed approach, model, or framework in detail
  4. Experiments / Results — Examine datasets, baselines, metrics, and reported outcomes
  5. Discussion & Limitations — Note any self-identified limitations
  6. Conclusion — Compare concluded claims against actual evidence presented

Step 1.3: Key Claims Extraction

List the paper's main claims explicitly:

Claim 1: [Specific claim about contribution or finding]
Evidence: [What evidence supports this claim in the paper]
Strength: [Strong / Moderate / Weak]

Claim 2: [...]
...

Phase 2: Critical Analysis

Step 2.1: Literature Context Search

Use web search to understand the research landscape:

Search queries:
- "[paper topic] state of the art [current year]"
- "[key method name] comparison benchmark"
- "[authors] previous work [topic]"
- "[specific technique] limitations criticism"
- "survey [research area] recent advances"

Use web_fetch on key related papers or surveys to understand where this work fits.

Step 2.2: Methodology Assessment

Evaluate the methodology using the following framework:

CriterionQuestions to AskRating
SoundnessIs the approach technically correct? Are there logical flaws?1-5
NoveltyWhat is genuinely new vs. incremental improvement?1-5
ReproducibilityAre details sufficient to reproduce? Code/data available?1-5
Experimental DesignAre baselines fair? Are ablations adequate? Are datasets appropriate?1-5
Statistical RigorAre results statistically significant? Error bars reported? Multiple runs?1-5
ScalabilityDoes the approach scale? Are computational costs discussed?1-5

Step 2.3: Contribution Significance Assessment

Evaluate the significance level:

LevelDescriptionCriteria
LandmarkFundamentally changes the fieldNew paradigm, widely applicable breakthrough
SignificantStrong contribution advancing the state of the artClear improvement with solid evidence
ModerateUseful contribution with some limitationsIncremental but valid improvement
MarginalMinimal advance over existing workSmall gains, narrow applicability
Below thresholdDoes not meet publication standardsFundamental flaws, insufficient evidence

Step 2.4: Strengths and Weaknesses Analysis

For each strength or weakness, provide:

  • What: Specific observation
  • Where: Section/figure/table reference
  • Why it matters: Impact on the paper's claims or utility

Phase 3: Review Synthesis

Step 3.1: Assemble the Structured Review

Produce the final review using the template below.

Review Output Template

# Paper Review: [Paper Title]

## Paper Metadata
- **Authors**: [Author list]
- **Venue**: [Publication venue or preprint server]
- **Year**: [Year]
- **Domain**: [Research field]
- **Paper Type**: [Empirical / Theoretical / Survey / Systems / Position]

## Executive Summary

[2-3 paragraph summary of the paper's core contribution, approach, and main findings.
State your overall assessment upfront: what the paper does well, where it falls short,
and whether the contribution is sufficient for the claimed venue/impact level.]

## Summary of Contributions

1. [First claimed contribution — one sentence]
2. [Second claimed contribution — one sentence]
3. [Additional contributions if any]

## Strengths

### S1: [Concise strength title]
[Detailed explanation with specific references to sections, figures, or tables in the paper.
Explain WHY this is a strength and its significance.]

### S2: [Concise strength title]
[...]

### S3: [Concise strength title]
[...]

## Weaknesses

### W1: [Concise weakness title]
[Detailed explanation with specific references. Explain the impact of this weakness on
the paper's claims. Suggest how it could be addressed.]

### W2: [Concise weakness title]
[...]

### W3: [Concise weakness title]
[...]

## Methodology Assessment

| Criterion | Rating (1-5) | Assessment |
|-----------|:---:|------------|
| Soundness | X | [Brief justification] |
| Novelty | X | [Brief justification] |
| Reproducibility | X | [Brief justification] |
| Experimental Design | X | [Brief justification] |
| Statistical Rigor | X | [Brief justification] |
| Scalability | X | [Brief justification] |

## Questions for the Authors

1. [Specific question that would clarify a concern or ambiguity]
2. [Question about methodology choices or alternative approaches]
3. [Question about generalizability or practical applicability]

## Minor Issues

- [Typos, formatting issues, unclear figures, notation inconsistencies]
- [Missing references that should be cited]
- [Suggestions for improved clarity]

## Literature Positioning

[How does this work relate to the current state of the art?
Are key related works cited? Are comparisons fair and comprehensive?
What important related work is missing?]

## Recommendations

**Overall Assessment**: [Accept / Weak Accept / Borderline / Weak Reject / Reject]

**Confidence**: [High / Medium / Low] — [Justification for confidence level]

**Contribution Level**: [Landmark / Significant / Moderate / Marginal / Below threshold]

### Actionable Suggestions for Improvement
1. [Specific, constructive suggestion]
2. [Specific, constructive suggestion]
3. [Specific, constructive suggestion]

Review Principles

Constructive Criticism

  • Always suggest how to fix it — Don't just point out problems; propose solutions
  • Give credit where due — Acknowledge genuine contributions even in flawed papers
  • Be specific — Reference exact sections, equations, figures, and tables
  • Separate minor from major — Distinguish fatal flaws from fixable issues

Objectivity Standards

  • ❌ "This paper is poorly written" (vague, unhelpful)
  • ✅ "Section 3.2 introduces notation X without formal definition, making the proof in Theorem 1 difficult to follow. Consider adding a notation table after the problem formulation." (specific, actionable)

Ethical Review Practices

  • Do NOT dismiss work based on author reputation or affiliation
  • Evaluate the work on its own merits
  • Flag potential ethical concerns (bias in datasets, dual-use implications) constructively
  • Maintain confidentiality of unpublished work

Adaptation by Paper Type

Paper TypeFocus Areas
EmpiricalExperimental design, baselines, statistical significance, ablations, reproducibility
TheoreticalProof correctness, assumption reasonableness, tightness of bounds, connection to practice
SurveyComprehensiveness, taxonomy quality, coverage of recent work, synthesis insights
SystemsArchitecture decisions, scalability evidence, real-world deployment, engineering contributions
PositionArgument coherence, evidence for claims, impact potential, fairness of characterizations

Common Pitfalls to Avoid

  • ❌ Reviewing the paper you wish was written instead of the paper that was submitted
  • ❌ Demanding additional experiments that are unreasonable in scope
  • ❌ Penalizing the paper for not solving a different problem
  • ❌ Being overly influenced by writing quality versus technical contribution
  • ❌ Treating absence of comparison to your own work as a weakness
  • ❌ Providing only a summary without critical analysis

Quality Checklist

Before finalizing the review, verify:

  • [ ] Paper was read completely (not just abstract and introduction)
  • [ ] All major claims are identified and evaluated against evidence
  • [ ] At least 3 strengths and 3 weaknesses are provided with specific references
  • [ ] The methodology assessment table is complete with ratings and justifications
  • [ ] Questions for authors target genuine ambiguities, not rhetorical critiques
  • [ ] Literature search was conducted to contextualize the contribution
  • [ ] Recommendations are actionable and constructive
  • [ ] The overall assessment is consistent with the identified strengths and weaknesses
  • [ ] The review tone is professional and respectful
  • [ ] Minor issues are separated from major concerns

Output Format

  • Output the complete review in Markdown format
  • Save the review to /mnt/user-data/outputs/review-{paper-topic}.md when working in sandbox
  • Present the review to the user using the present_files tool

Notes

  • This skill complements the deep-research skill — load both when the user wants the paper reviewed in the context of the broader field
  • For papers behind paywalls, work with whatever content is accessible (abstract, publicly available versions, preprint mirrors)
  • Adapt the review depth to the user's needs: a brief assessment for quick triage versus a full review for submission preparation
  • When reviewing multiple papers comparatively, maintain consistent criteria across all reviews
  • Always disclose limitations of your review (e.g., "I could not verify the proofs in Appendix B in detail")

质量与来源

所属仓库
bytedance/deer-flow
仓库星标
8.4 万
最近更新
今天
采集时间
今天
commit
b346b17fce89
内容指纹
sha256:a0285baaeacc916
文件路径
skills/public/academic-paper-review/SKILL.md

同仓库其它 Skill

查看全部 32 个
blocking-io-guard
Ensure async-path backend code that could block the asyncio event loop is protected by a teeth-verified runtime anchor in tests/blocking_io/. Use when changing backend Python under app/, packages/harness/deerflow/, or scripts/, when running a blocking-IO triage round over the whole repo, or when a reviewer/CI asks for blocking-IO coverage. Runs a deterministic scan (changed-lines or full-repo), routes each candidate, drafts/extends an anchor, and proves it fails when the blocking IO regresses.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
deerflow-maintainer-orchestrator
Use when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review comments, review PR or issue batches, compare competing PRs that target the same issue, give fix strategy, risk classification, and validation guidance. Intended for maintainers and trusted local agents, not general contributors.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
engineer-system-change
Evaluate and carry out non-trivial software-system changes from first principles. Use when assessing RFCs, issues, designs, features, refactors, migrations, dependency changes, or proposed fields, events, APIs, modules, and services whose need, consumers, system fit, validation, or rollback require scrutiny. Read the actual system, identify the concrete problem and named semantic consumers, choose the smallest sufficient solution, reject pseudo-requirements and speculative abstractions, and require evidence proportional to risk. Do not use for mechanical edits, source-code explanation, or a dedicated review of an already-complete diff.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke test deployment", "verify installation", "test service availability", "end-to-end test", or similar.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
bootstrap
Generate a personalized SOUL.md through a warm, adaptive onboarding conversation. Trigger when the user wants to create, set up, or initialize their AI partner's identity — e.g., "create my SOUL.md", "bootstrap my agent", "set up my AI partner", "define who you are", "let's do onboarding", "personalize this AI", "make you mine", or when a SOUL.md is missing. Also trigger for updates: "update my SOUL.md", "change my AI's personality", "tweak the soul".
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端
chart-visualization
This skill should be used when the user wants to visualize data. It intelligently selects the most suitable chart type from 26 available options, extracts parameters based on detailed specifications, and generates a chart image using a JavaScript script.
精选 bytedance/deer-flow 8.4 万 原文
Codex CLIMCP 客户端

相似 Skill

更多「研究」
last30days
Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.
精选 mvanhorn/last30days-skill 6.4 万 原文
Claude CodeCodex CLIMCP 客户端
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram, V2EX, LinkedIn/领英/Boss直聘/招聘/求职/jobs, YouTube, GitHub code search, 小宇宙播客, 雪球/股票行情, RSS feeds, or any web URL. 16 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: 写报告/数据分析/翻译等内容加工(本 skill 只负责从互联网获取内容); 发帖/评论/点赞等写操作;已有专门 skill 的平台(先用专门 skill)。 【路由方式】SKILL.md 包含路由表和常用命令,复杂场景需按需阅读对应分类的 references/*.md。 分类:search / social (小红书/推特/B站/V2EX/Reddit/Facebook/Instagram) / career(LinkedIn/Boss直聘) / dev(github) / web(网页/文章/RSS) / video(YouTube/B站/播客) / finance(雪球/股票)。
精选 Panniantong/Agent-Reach 9.6 万 原文
Claude CodeCursorMCP 客户端
academic-paper-reviewer
Multi-perspective academic paper review with dynamic reviewer personas. Runs a 5-seat, role-separated review panel (Journal-Fit Reviewer + 3 peer-review roles + Devil's Advocate) with field-specific expertise; role separation is not a claim of independent error processes. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy, 審查論文, 論文審查, 模擬審查, 同儕審查, 幫我審這篇, 以審查人角度評估, 審查者校準, 논문 심사, 동료 심사, 모의 심사, 심사자 관점에서 평가, 심사자 보정, revisar artículo, revisión entre pares, revisión de manuscrito, informe de árbitro, revisa mi artículo, criticar artículo, simular revisión, revisión editorial, calibrar revisor.
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code
academic-paper
12-agent academic paper writing pipeline. 11 modes (full/plan/outline/revision/revision-coach/abstract/lit-review/format-convert/citation-check/disclosure/rebuttal-audit). 6 paper types, 5 citation formats, bilingual abstracts, LaTeX/DOCX-via-Pandoc/PDF output. Style Calibration + Writing Quality Check + Anti-Patterns with IRON RULE markers. Triggers: write paper, academic paper, guide my paper, parse reviews, I got reviewer comments, revision roadmap, should we push back, conference rebuttal, grant panel response, audit my rebuttal, check my response draft, AI disclosure, check citations, citation check, check my references, verify references, look over the refs, 寫論文, 學術論文, 引導我寫論文, 審查意見, 我收到審查意見, 修訂路線圖, 評估回覆, 檢查引用, 引用檢查, 檢查參考文獻, 核對文獻, 논문 작성, 초록 작성, 논문 수정, 논문 계획을 도와줘, 심사 의견을 받았어, 심사 의견 반영, 답변서 점검, AI 사용 고지, 인용 확인, 인용 형식 검사, enmendar mi artículo, redactar artículo, guía mi artículo, analizar reseñas, auditar mi respuesta, verificar borrador de respuesta, verificar citas, divulgación de IA.
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code
academic-pipeline
Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory, coverage-bounded integrity checks, two-stage peer review, and auditable quality-assurance artifacts. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow, 연구부터 논문까지, 연구 주제 설정부터 논문 완성까지, 논문 전체 워크플로, flujo de trabajo académico, investigación a artículo, flujo completo de artículo, pipeline de investigación completa, publicación de investigación, flujo de trabajo completo del artículo.
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code
deep-research
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 8 modes: full research, quick brief, paper review, lit-review, fact-check, three-way literature scan, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review, devil's advocate challenges, ethics review, and post-research literature monitoring. Triggers on: research, deep research, literature review, systematic review, meta-analysis, PRISMA, evidence synthesis, fact-check, WHY HOW WHAT papers, 3W literature scan, guide my research, help me think through, 研究, 深度研究, 文獻回顧, 文獻探討, 系統性回顧, 後設分析, 事實查核, 三段式文獻掃描, 引導我的研究, 幫我釐清, 幫我想想, 我不確定要研究什麼, 研究方向, 研究主題, 심층 연구, 문헌 조사, 체계적 문헌고찰, 메타분석, 사실 확인, 연구 방향을 잡아줘, 연구 주제 정하는 것을 도와줘, revisión de literatura, metaanálisis
精选 Imbad0202/academic-research-skills 5.2 万 原文
Claude Code