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".
What this skill does
# 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: | Field | Description | |-------|-------------| | **Title** | Full paper title | | **Authors** | Author list and affiliations | | **Venue / Status** | Publication venue, preprint server, or submission status | | **Year** | Publication or submission year | | **Domain** | Research field and subfield | | **Paper Type** | Empirical, 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: | Criterion | Questions to Ask | Rating | |-----------|-----------------|--------| | **Soundness** | Is the approach technically correct? Are there logical flaws? | 1-5 | | **Novelty** | What is genuinely new vs. incremental improvement? | 1-5 | | **Reproducibility** | Are details sufficient to reproduce? Code/data available? | 1-5 | | **Experimental Design** | Are baselines fair? Are ablations adequate? Are datasets appropriate? | 1-5 | | **Statistical Rigor** | Are results statistically significant? Error bars reported? Multiple runs? | 1-5 | | **Scalability** | Does the approach scale? Are computational costs discussed? | 1-5 | #### Step 2.3: Contribution Significance Assessment Evaluate the significance level: | Level | Description | Criteria | |-------|-------------|----------| | **Landmark** | Fundamentally changes the field | New paradigm, widely applicable breakthrough | | **Significant** | Strong contribution advancing the state of the art | Clear improvement with solid evidence | | **Moderate** | Useful contribution with some limitations | Incremental but valid improvement | | **Marginal** | Minimal advance over existing work | Small gains, narrow applicability | | **Below threshold** | Does not meet publication standards | Fundamental 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 ```markdown # 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 sug
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.