mcpbeat Sign in

Academic Paper Review Agent Skill

Structured peer-review of academic papers.

2k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
117
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HezaoHezao/poirot --skill academic-paper-review

The instruction itself

19 sections, as written by the author

Academic Paper Review

Overview

Produces structured, peer-review-quality analyses of academic papers. Follows

review standards used by top-tier venues (NeurIPS, ICML, ACL, Nature, IEEE) to

provide rigorous, constructive, and balanced assessments.

Covers **summary, strengths, weaknesses, methodology assessment, contribution

evaluation, literature positioning, and actionable recommendations** — all

grounded in evidence from the paper itself.

When to Use

  • User provides a paper URL (arXiv, DOI, conference proceedings)
  • User asks to "review", "analyze", "critique", "assess", or "summarize" a

research paper

  • User wants to understand strengths and weaknesses of a study
  • User requests a peer-review-style evaluation

Review Methodology

Phase 1: Paper Comprehension

Step 1.1: Identify Paper Metadata

Extract: Title, Authors, Venue/Status, Year, Domain, Paper Type (Empirical /

Theoretical / Survey / Systems / Position).

Step 1.2: Deep Reading Pass

Read the paper systematically using browse_page:

  • Abstract & Introduction — Identify claimed contributions and motivation
  • Related Work — Note how authors position relative to prior art
  • Methodology — Understand the proposed approach in detail
  • Experiments / Results — Examine datasets, baselines, metrics, outcomes
  • Discussion & Limitations — Note self-identified limitations
  • Conclusion — Compare concluded claims against actual evidence
Step 1.3: Key Claims Extraction

List the paper's main claims explicitly:

Claim 1: [Specific claim]
Evidence: [What evidence supports this]
Strength: [Strong / Moderate / Weak]

Phase 2: Critical Analysis

Use web_search to understand the research landscape:

"[paper topic] state of the art [current year]"
"[key method name] comparison benchmark"
"[specific technique] limitations criticism"

Use browse_page on key related papers or surveys.

Step 2.2: Methodology Assessment

| Criterion | Questions to Ask | Rating |

|-----------|-----------------|--------|

| Soundness | Is the approach technically correct? | 1-5 |

| Novelty | What is genuinely new vs incremental? | 1-5 |

| Reproducibility | Are details sufficient? Code/data available? | 1-5 |

| Experimental Design | Are baselines fair? Ablations adequate? | 1-5 |

| Statistical Rigor | Results significant? Error bars? Multiple runs? | 1-5 |

| Scalability | Does it scale? Computational costs discussed? | 1-5 |

Step 2.3: Contribution Significance

| Level | Description |

|-------|-------------|

| Landmark | Fundamentally changes the field |

| Significant | Strong contribution advancing state of the art |

| Moderate | Useful contribution with some limitations |

| Marginal | Minimal advance over existing work |

| Below threshold | Does not meet publication standards |

Phase 3: Review Synthesis

Produce the final review using this 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 core contribution, approach, and main findings.
State overall assessment upfront.]

## Summary of Contributions
1. [First claimed contribution]
2. [Second claimed contribution]

## Strengths
### S1: [Concise strength title]
[Detailed explanation with specific references to sections, figures, tables.]

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

## Weaknesses
### W1: [Concise weakness title]
[Detailed explanation. Explain impact. Suggest how to address.]

### W2: [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]
2. [Question about methodology choices]

## Literature Positioning
[How does this work relate to current state of the art? Key related works cited?]

## Recommendations
**Overall Assessment**: [Accept / Weak Accept / Borderline / Weak Reject / Reject]
**Confidence**: [High / Medium / Low]
**Contribution Level**: [Landmark / Significant / Moderate / Marginal / Below threshold]

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

Review Principles

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

(specific, actionable)

Adaptation by Paper Type

| Paper Type | Focus Areas |

|------------|-------------|

| Empirical | Experimental design, baselines, statistical significance, ablations |

| Theoretical | Proof correctness, assumption reasonableness, tightness of bounds |

| Survey | Comprehensiveness, taxonomy quality, coverage of recent work |

| Systems | Architecture decisions, scalability evidence, real-world deployment |

| Position | Argument coherence, evidence for claims, impact potential |

Common Pitfalls

  • ❌ Reviewing the paper you wish was written instead of the paper 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
  • ❌ Providing only a summary without critical analysis

Quality Checklist

  • [ ] Paper read completely (not just abstract and introduction)
  • [ ] All major claims identified and evaluated against evidence
  • [ ] At least 3 strengths and 3 weaknesses with specific references
  • [ ] Methodology assessment table complete with ratings and justifications
  • [ ] Literature search conducted to contextualize the contribution
  • [ ] Recommendations are actionable and constructive
  • [ ] Review tone is professional and respectful

Output

  • Output the complete review in Markdown
  • Save to .poirot/outputs/review-{paper-topic}.md via write_file
  • Present to user via present_files

Other skills for the same job

different authors, same section of the catalogue
Content Research Writer
by frostant
×10

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

4k tokens
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Notebooklm
by ZhanlinCui
×6

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

26k tokens scripts
Biorxiv Database
by christophacham
×4

Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.

9k tokens scripts
Openalex Database
by christophacham
×4

Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.

13k tokens scripts
Uspto Database
by christophacham
×4

Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

21k tokens scripts
Denario
by christophacham
×3

Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.

11k tokens
Hypogenic
by christophacham
×3

Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.

7k tokens

How to use it

Copy the folder

Take hezaohezao/academic-paper-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.