review-paper
Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections
Best use case
review-paper is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections
Teams using review-paper should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/review-paper/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How review-paper Compares
| Feature / Agent | review-paper | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Comprehensive manuscript review covering argument structure, econometric specification, citation completeness, and potential referee objections
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
# Manuscript Review Produce a thorough, constructive review of an academic manuscript — the kind of report a top-journal referee would write. **Input:** `$ARGUMENTS` — path to a paper (.tex, .pdf, or .qmd), or a filename in `master_supporting_docs/`. --- ## Steps 1. **Locate and read the manuscript.** Check: - Direct path from `$ARGUMENTS` - `master_supporting_docs/supporting_papers/$ARGUMENTS` - Glob for partial matches 2. **Read the full paper** end-to-end. For long PDFs, read in chunks (5 pages at a time). 3. **Evaluate across 6 dimensions** (see below). 4. **Generate 3-5 "referee objections"** — the tough questions a top referee would ask. 5. **Produce the review report.** 6. **Save to** `quality_reports/paper_review_[sanitized_name].md` --- ## Review Dimensions ### 1. Argument Structure - Is the research question clearly stated? - Does the introduction motivate the question effectively? - Is the logical flow sound (question → method → results → conclusion)? - Are the conclusions supported by the evidence? - Are limitations acknowledged? ### 2. Identification Strategy - Is the causal claim credible? - What are the key identifying assumptions? Are they stated explicitly? - Are there threats to identification (omitted variables, reverse causality, measurement error)? - Are robustness checks adequate? - Is the estimator appropriate for the research design? ### 3. Econometric Specification - Correct standard errors (clustered? robust? bootstrap?)? - Appropriate functional form? - Sample selection issues? - Multiple testing concerns? - Are point estimates economically meaningful (not just statistically significant)? ### 4. Literature Positioning - Are the key papers cited? - Is prior work characterized accurately? - Is the contribution clearly differentiated from existing work? - Any missing citations that a referee would flag? ### 5. Writing Quality - Clarity and concision - Academic tone - Consistent notation throughout - Abstract effectively summarizes the paper - Tables and figures are self-contained (clear labels, notes, sources) ### 6. Presentation - Are tables and figures well-designed? - Is notation consistent throughout? - Are there any typos, grammatical errors, or formatting issues? - Is the paper the right length for the contribution? --- ## Output Format ```markdown # Manuscript Review: [Paper Title] **Date:** [YYYY-MM-DD] **Reviewer:** review-paper skill **File:** [path to manuscript] ## Summary Assessment **Overall recommendation:** [Strong Accept / Accept / Revise & Resubmit / Reject] [2-3 paragraph summary: main contribution, strengths, and key concerns] ## Strengths 1. [Strength 1] 2. [Strength 2] 3. [Strength 3] ## Major Concerns ### MC1: [Title] - **Dimension:** [Identification / Econometrics / Argument / Literature / Writing / Presentation] - **Issue:** [Specific description] - **Suggestion:** [How to address it] - **Location:** [Section/page/table if applicable] [Repeat for each major concern] ## Minor Concerns ### mc1: [Title] - **Issue:** [Description] - **Suggestion:** [Fix] [Repeat] ## Referee Objections These are the tough questions a top referee would likely raise: ### RO1: [Question] **Why it matters:** [Why this could be fatal] **How to address it:** [Suggested response or additional analysis] [Repeat for 3-5 objections] ## Specific Comments [Line-by-line or section-by-section comments, if any] ## Summary Statistics | Dimension | Rating (1-5) | |-----------|-------------| | Argument Structure | [N] | | Identification | [N] | | Econometrics | [N] | | Literature | [N] | | Writing | [N] | | Presentation | [N] | | **Overall** | **[N]** | ``` --- ## Principles - **Be constructive.** Every criticism should come with a suggestion. - **Be specific.** Reference exact sections, equations, tables. - **Think like a referee at a top-5 journal.** What would make them reject? - **Distinguish fatal flaws from minor issues.** Not everything is equally important. - **Acknowledge what's done well.** Good research deserves recognition. - **Do NOT fabricate details.** If you can't read a section clearly, say so.
Related Skills
review-r
Run the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files.
pedagogy-review
Run holistic pedagogical review on lecture slides. Checks narrative arc, student prerequisites, worked examples, notation clarity, and deck pacing.
lit-review
Structured literature search and synthesis with citation extraction and gap identification
visual-audit
Perform adversarial visual audit of Quarto or Beamer slides checking for overflow, font consistency, box fatigue, and layout issues.
validate-bib
Validate bibliography entries against citations in all lecture files. Find missing entries and unused references.
translate-to-quarto
Translate Beamer LaTeX to Quarto RevealJS. Multi-phase workflow with TikZ extraction and QA.
slide-excellence
Multi-agent slide review (visual, pedagogy, proofreading). Use for comprehensive quality check before milestones.
research-ideation
Generate structured research questions, testable hypotheses, and empirical strategies from a topic or dataset
qa-quarto
Adversarial Quarto vs Beamer QA. Critic finds issues, fixer applies fixes, loops until APPROVED (max 5 rounds).
proofread
Run the proofreading protocol on lecture files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.
learn
Extract reusable knowledge from the current session into a persistent skill. Use when you discover something non-obvious, create a workaround, or develop a multi-step workflow that future sessions would benefit from.
interview-me
Interactive interview to formalize a research idea into a structured specification with hypotheses and empirical strategy