본문으로 건너뛰기
cccskills
무료GitHub에 공개

academic-paper-review

Turn academic papers into structured reviews that explain findings, strengths, weaknesses, and research methods. Assess originality and supporting evidence, compare relevant literature, and provide specific improvement suggestions in a detailed review or brief summary.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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".

설치 방법 보기

이럴 때 유용합니다

  • Understanding a paper's findings and limitations
  • Preparing a draft peer review
  • Checking experimental design and reproducibility
  • Comparing papers using consistent criteria

포함된 파일(1)

  • SKILL.md11.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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")

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Find Python input/output calls that may stall asynchronous backend work, then fix or guard each relevant path with runtime tests. Verify that tests fail when blocking behavior returns and pass after the fix is restored.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking asynchronous Python changes before a pull request
  • Triaging blocking input/output across the codebase
  • Adding tests for cleanup and error branches
bytedance/deer-flow8.4만2026년 10월 19일 업데이트

bootstrap

무료

Create or update a SOUL.md file that defines an AI partner’s behavior through a guided conversation. Clarify communication style, autonomy, honesty, and expectations, then review a concise English profile before saving it with setup_agent.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Define an AI partner’s initial personality and role
  • Adjust tone and how the AI expresses disagreement
  • Clarify which decisions the AI can make independently
bytedance/deer-flow8.4만2026년 10월 19일 업데이트

Turn data into chart images by selecting a suitable format from 26 options. Visualize trends, comparisons, distributions, flows, or relationships, then receive the image URL and the complete settings used to generate it.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Visualize changes over time
  • Compare categories and proportions
  • Show distributions and correlations
bytedance/deer-flow8.4만2026년 10월 19일 업데이트

Send research and analysis tasks to a running DeerFlow instance through its HTTP API, an interface for exchanging requests. Retrieve responses, continue conversations, upload documents, and inspect available models, skills, agents, and service health.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Delegate research and analysis to DeerFlow
  • Upload documents for a conversation
  • Resume an earlier conversation
bytedance/deer-flow8.4만2026년 10월 19일 업데이트

Turn source code into project documentation, from a README with installation steps and examples to API references, architecture diagrams, developer guides, and changelogs. Match the scope and comment format to the project's size and programming language.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating a README with installation steps and usage examples
  • Documenting public functions, parameters, and return values
  • Preparing architecture and contributor guides for new developers
bytedance/deer-flow8.4만2026년 10월 19일 업데이트

Plan market, competitor, consumer, or financial research with chapter outlines, data requirements, and chart plans. Then turn collected evidence into a structured Markdown report with comparisons, citations, and strategic implications, while clearly identifying missing data.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Planning research chapters and data collection requirements
  • Turning market and competitor findings into a report
  • Organizing consumer insights and brand strategy analysis
bytedance/deer-flow8.4만2026년 10월 19일 업데이트

bytedance의 스킬 모두 보기

이 스킬의 문제 신고