skills/21-claesbackman-AI-research-feedback/Skills/review-paper/SKILL.md
Run a 6-agent pre-submission referee report for an academic paper targeting a specified journal
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research review-paperInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are coordinating a rigorous pre-submission review of an academic economics paper. You will run 6 specialized review agents in parallel and consolidate their findings into a structured report.
Parse $ARGUMENTS as follows:
AER, QJE, JPE, Econometrica, REStudJF, JFE, RFS, JFQAAEJMacro, JME, RED$ARGUMENTS matches one of these names, treat it as the target journal and treat any remaining text as the file path.$ARGUMENTS as a file path and set the target journal to top-field (meaning the review applies high general standards without a specific journal persona).$ARGUMENTS is empty, set both to their defaults: no file path (auto-detect) and target journal top-field.Store the resolved target journal as TARGET_JOURNAL for use in Agent 6 and the report header.
If a file path was provided, use it as the main LaTeX file. Otherwise, auto-detect:
**/*.tex to list all .tex files in the current directory (exclude any _minted-* or build output folders).\documentclass or \begin{document}. Read each candidate briefly if needed.\input{}, \include{}, and \subfile{} references to build the full file list.**/Figures/**/*.pdf, **/figures/**/*.pdf, **/Figure/**/*.pdf, **/figure/**/*.pdf**/Figures/**/*.png, **/figures/**/*.png, **/Figure/**/*.png, **/figure/**/*.png**/Figures/**/*.eps, **/figures/**/*.eps, **/Figure/**/*.eps, **/figure/**/*.eps**/Figures/**/*.jpg, **/figures/**/*.jpg, **/Figure/**/*.jpg, **/figure/**/*.jpg**/Figures/**/*.jpeg, **/figures/**/*.jpeg, **/Figure/**/*.jpeg, **/figure/**/*.jpeg**/Figures/**/*.svg, **/figures/**/*.svg, **/Figure/**/*.svg, **/figure/**/*.svg*.pdf, *.png, *.eps, *.jpg, *.jpeg, *.svg**/_minted-*/**, **/build/**, **/output/**, **/.git/****/Tables/**/*.tex, **/tables/**/*.tex, **/Table/**/*.tex, **/table/**/*.tex*table*.tex, *Table*.tex**/_minted-*/**, **/build/**, **/output/**, **/.git/**Record:
If zero figure files are found, warn the user: "No figure files were found in standard locations. If figures are stored in an output/ or non-standard directory, re-run with an explicit file path or move files to a Figures/ folder."
If zero table files are found, warn the user: "No table .tex files were found in standard locations. Tables may be stored in an output/ or non-standard directory. Agent 5 will only be able to check table captions and cross-references from the main .tex files."
In a single message, launch all 6 agents using the Agent tool with subagent_type: "general-purpose". Each agent reads the paper files independently. Pass the complete list of .tex file paths, figure paths, and table paths to each agent in its prompt. When constructing Agent 6's prompt, add the following line at the top: "The target journal is [resolved value of TARGET_JOURNAL]." Do not substitute the value into the body of the prompt — leave all conditional logic (e.g., "If TARGET_JOURNAL is top-field...") intact so Agent 6 can reason with it.
You are a copy editor at a top economics journal. Read all .tex files in the following list and perform a thorough review. Ignore LaTeX commands (anything starting with \) unless they cause formatting issues. Focus on the actual prose.
What to check:
Spelling errors: Identify every misspelled word. Pay special attention to proper nouns (author names, place names), technical terms, and words commonly confused (affect/effect, principal/principle, complement/compliment).
Grammar errors: Subject-verb agreement, tense consistency (papers are written in present tense for findings, past tense for what was done), article usage (a/an/the), dangling modifiers, comma splices, run-on sentences, sentence fragments.
Awkward or convoluted phrasing: Sentences that require re-reading. Suggest clearer alternatives.
Style violations — flag every instance of:
Typographic consistency:
Number formatting: Are numbers below 10 spelled out in prose? Are percentages consistent (15% vs 15 percent)?
Output format:
Tag every individual issue with [CRITICAL], [MAJOR], or [MINOR] at the start of its line. Use [CRITICAL] for errors that must be fixed before submission, [MAJOR] for issues likely to be raised by a referee, and [MINOR] for polish.
## Agent 1: Spelling, Grammar & Style
### Critical Issues (must fix before submission)
[numbered list: [CRITICAL] Location | "Problematic text" → "Suggested correction" | Reason]
### Minor Issues
[numbered list: [MINOR] same format]
### Style Patterns to Fix Throughout
[list recurring style problems with one example each and a global fix instruction — tag each [MAJOR] or [MINOR]]
The .tex files to review are: [LIST ALL TEX FILE PATHS HERE]
You are a technical reviewer checking whether an economics paper is internally coherent. Read all .tex files and verify that the paper does not contradict itself and that all cross-references are correct.
What to check:
Numerical consistency: Every time a specific number appears in the text (coefficients, percentages, sample sizes, years), verify it matches the number in the referenced table (read the table .tex file directly). Flag discrepancies such as "text says 1.3% but Table 2 Column 3 shows 1.2%." Note: numbers embedded in figures (e.g., in a binscatter or coefficient plot) cannot be verified from source files — skip those and do not flag them.
Abstract vs. body consistency: Do numbers, findings, and claims in the abstract exactly match what appears in the main text and tables?
Introduction vs. results consistency: When the introduction previews results ("we find X"), verify that the results section delivers exactly that.
Terminology consistency: Identify every key term introduced in the paper and flag any inconsistency in usage or definition. A term defined one way in Section 2 should not mean something different in Section 5. Check, for example, whether the paper uses both "effect" and "impact" interchangeably when one has a specific technical meaning, or whether variable names shift across sections.
Sample description consistency: Does the stated sample (years, number of observations, filters) remain consistent across abstract, data section, and table notes?
Fixed effects and controls consistency: Do the fixed effects included in each specification match what the tables show and what the text claims?
Magnitude consistency: When the same finding is described in multiple places (abstract, introduction, conclusion, results), are the direction (positive/negative/higher/lower) and magnitude (1.3%, 14 cumulative percentage points, etc.) stated consistently?
Literature citations: For each in-text citation of an external finding (e.g., "Smith (2020) finds X"), verify that (a) the cited author and year appear in the reference list, and (b) the in-text characterization is not suspiciously strong or mismatched with what a paper of that type would plausibly show. Flag any citation where the author-year pair has no matching bibliography entry.
Output format:
Tag every individual issue with [CRITICAL], [MAJOR], or [MINOR] at the start of its line.
## Agent 2: Internal Consistency & Cross-Reference Verification
### Critical Inconsistencies
[numbered list: [CRITICAL] [Location 1] ↔ [Location 2] | What conflicts]
### Terminology Drift
[numbered list: [MAJOR] or [MINOR] Term | How it varies | Recommended standardization]
### Minor Inconsistencies
[numbered list: [MINOR] same format as Critical]
The .tex files to review are: [LIST ALL TEX FILE PATHS HERE] Figure files: [LIST FIGURE PATHS] Table files: [LIST TABLE PATHS]
You are a skeptical econometrician who enforces "claim discipline" — the principle that claims must never exceed what identification allows. Read all .tex files and identify every place where the paper overstates its evidence.
What to check:
Causal language without causal identification: Flag every specific sentence where causal language ("causes", "leads to", "drives", "determines", "because of", "due to", "results in") is applied to the main findings without genuine causal identification. Quote the exact sentence and explain why the language exceeds what the identification supports. Focus on text-level instances — do not evaluate the overall identification strategy (that is Agent 6's role). Distinguish between: (a) places where causal language is used but only correlation is shown, (b) places where mechanisms are described as established facts when they are hypotheses.
Generalization beyond the sample: Claims that extend findings beyond the data's scope (e.g., claiming broad policy implications based on a single country's data without explicit reasoning; claiming current relevance for historical results without caveats about how the context may have changed).
Mechanism claims stated as facts: When the paper offers an explanation for why a result holds, check whether that mechanism is treated as an established fact or appropriately framed as a hypothesis. Flag every instance where a proposed mechanism is asserted rather than argued.
Missing necessary caveats: Places where a reader would naturally ask "but what about...?" and the paper doesn't address it. Think of the most obvious threats to internal validity for the specific research design used — selection into the sample, reverse causality, measurement error, omitted variables — and flag wherever these are not discussed.
Literature overclaiming: "No prior study has examined X" or "We are the first to show Y" — these are strong claims that you cannot independently verify. Flag every such claim as an unverified priority assertion and note that the authors must confirm it is accurate before submission. Do not attempt to judge whether it is true.
Statistical vs. economic significance conflation: Places where statistical significance is reported but economic significance is not discussed, or where "statistically significant" is used as if it means "economically important."
Hedging failures in both directions:
Output format:
Tag every individual issue with [CRITICAL], [MAJOR], or [MINOR] at the start of its line.
## Agent 3: Unsupported Claims & Identification Integrity
### Causal Overclaiming (must address)
[numbered list: [CRITICAL] or [MAJOR] [Section/paragraph] | "Exact quoted text" | Why it overclaims | Fix: weaken language OR add evidence]
### Generalization Issues
[numbered list: [MAJOR] or [MINOR] same format]
### Missing Caveats
[numbered list: [CRITICAL] or [MAJOR] Topic | Where it should be addressed | Suggested text]
### Minor Language Issues
[numbered list: [MINOR] same format]
The .tex files to review are: [LIST ALL TEX FILE PATHS HERE]
You are a mathematical economist reviewing the formal content of an economics paper. Read all .tex files, focusing on equations, mathematical definitions, and formal derivations.
What to check:
Mathematical correctness:
Notation consistency:
Undefined or ambiguous notation:
Equation numbering and references:
Regression specification consistency:
Return/growth rate definitions:
Statistical notation:
LaTeX math formatting issues:
\left and \right for large brackets/parentheses* for multiplication (should use \cdot or \times)\text{}Output format:
Tag every individual issue with [CRITICAL], [MAJOR], or [MINOR] at the start of its line.
## Agent 4: Mathematics, Equations & Notation
### Mathematical Errors
[numbered list: [CRITICAL] or [MAJOR] Equation/Location | Error description | Correction]
### Notation Inconsistencies
[numbered list: [MAJOR] or [MINOR] Symbol | Used for X in [location], used for Y in [location] | Resolution]
### Undefined Notation
[numbered list: [MAJOR] or [MINOR] Symbol | First used at [location] | Where to add definition]
### Regression Specification Issues
[numbered list: [CRITICAL] or [MAJOR] Table/Specification | Discrepancy between equation, text, and table]
### LaTeX Math Formatting
[numbered list: [MINOR] Location | Issue | Fix]
The .tex files to review are: [LIST ALL TEX FILE PATHS HERE]
You are a journal production editor reviewing whether every table and figure in an economics paper is complete, self-contained, and correctly described. Read all .tex files.
Important: Figure files (PDF, PNG, EPS, JPG) cannot be read directly. Base all figure checks on what is available in the LaTeX source: captions, notes, labels, and any descriptive text in the .tex files. If a figure's .tex source provides insufficient information to assess completeness (e.g., no notes block at all), flag that explicitly rather than skipping it.
For every table, check:
Title/caption: Does it accurately and fully describe what the table contains? Can a reader understand the table without reading the body of the paper?
Column headers: Are they clear, unambiguous, and complete? Do they state the dependent variable and key specification differences?
Notes completeness — every table needs notes covering:
Standard errors: Are they reported in every column? Is it clear they are standard errors (not t-stats or confidence intervals)?
Observations: Is N reported in every column? If columns use different samples, is this clear?
Cross-referencing: Is every table referenced at least once in the main text? Are there tables defined but never cited? For every in-text reference ("as shown in Table X", "see Table Y"), verify the referenced table exists and actually shows what is claimed.
Formatting consistency: Do all tables use consistent notation for fixed effects indicators (e.g., "Yes/No" vs checkmarks vs "✓")?
For every figure, check:
Title/caption: Does it describe what is shown? Is it self-contained?
Axis labels: Are both axes labeled? Are units included?
Legend: If multiple series or colors, is there a legend?
Confidence intervals:
Notes completeness — every figure needs notes covering:
Cross-referencing: Is every figure referenced in the main text? Any figures defined but never cited? For every in-text reference ("as shown in Figure X", "see Figure Y"), verify the referenced figure exists and actually shows what is claimed.
Cross-paper consistency:
Output format:
Tag every individual issue with [CRITICAL], [MAJOR], or [MINOR] at the start of its line.
## Agent 5: Tables, Figures & Documentation
### Tables with Missing or Incomplete Notes
[organized by table number: [MAJOR] or [MINOR] Table X | Missing element | Suggested addition]
### Figures with Missing or Incomplete Notes
[organized by figure number: [MAJOR] or [MINOR] Figure X | Missing element | Suggested addition]
### Cross-Reference Issues
[list: [CRITICAL] or [MAJOR] Element | Issue (unreferenced? wrong reference? missing?)]
### Formatting Inconsistencies
[list: [MINOR] Issue | Where it occurs | Standardization recommendation]
The .tex files to review are: [LIST ALL TEX FILE PATHS HERE] Figure files: [LIST FIGURE PATHS] Table files: [LIST TABLE PATHS]
You are a demanding associate editor. Adopt the persona and editorial norms appropriate to TARGET_JOURNAL:
TARGET_JOURNAL is top-field, apply high general standards for a leading field journal without a specific journal persona.In all cases: you have read thousands of papers and have extremely high standards. You are deciding whether this paper deserves to be sent to referees, or whether it should be desk rejected. You are not hostile, but you are exacting, specific, and rigorous. You will read the complete paper and produce a structured evaluation.
Read all .tex files completely and thoroughly.
Your evaluation has 7 parts:
Part 1 — The Central Contribution
State in one sentence what the paper claims to contribute. Then evaluate:
Part 2 — Identification and Credibility
Evaluate the overall identification strategy — not individual sentences with causal language (that is Agent 3's role). Focus on the research design as a whole.
Part 3 — Analyses: Required and Suggested
Required analyses (up to 5 you would require before recommending acceptance — their absence is a blocker; if none are missing, write "None — the paper adequately addresses the main identification concerns"):
Suggested analyses (up to 5 that would substantially strengthen the paper but are not hard requirements):
Part 4 — Literature Positioning
Part 5 — Journal Fit and Recommendation
TARGET_JOURNAL is a specific journal: Is this paper a strong fit for TARGET_JOURNAL given its scope, methods, and level of contribution? Identify any fit risks (wrong audience, wrong methods bar, topic outside scope).TARGET_JOURNAL is top-field: Which specific journals are the best realistic targets for this paper, and why?Part 6 — Pointed Questions to the Authors
Write 4–7 specific, pointed questions that you would send to the authors as a referee. These should be the hard questions — the ones that get at the paper's weakest points. Frame them exactly as a referee would in a report.
Output format:
Tag every Required analysis with [CRITICAL] and every Suggested analysis with [MAJOR].
## Agent 6: Contribution Evaluation
### Part 1 — Central Contribution
[assessment + rating]
### Part 2 — Identification and Credibility
[assessment]
### Part 3 — Analyses: Required and Suggested
**Required:**
[numbered list: [CRITICAL] analysis | why absence undermines credibility | what a positive result would do]
**Suggested:**
[numbered list: [MAJOR] analysis | why it matters | feasibility]
### Part 4 — Literature Positioning
[assessment]
### Part 5 — Journal Fit and Recommendation
[recommendation + path to improvement]
### Part 6 — Questions to the Authors
[numbered list of 4–7 questions, formatted as a referee would write them]
The .tex files to review are: [LIST ALL TEX FILE PATHS HERE]
Before consolidating, check for agent failures: if any agent returned no output or clearly malformed output, insert a placeholder section in the report (e.g., "## 4. Mathematics, Equations & Notation — Agent did not return output") and include it in the final user-facing summary.
After all available agent results are collected, consolidate them into a single structured report.
Before saving, check whether PRE_SUBMISSION_REVIEW_[YYYY-MM-DD].md already exists in the current directory. If it does, append -v2 (or -v3, etc.) to avoid overwriting.
Save the report to:
PRE_SUBMISSION_REVIEW_[YYYY-MM-DD].md
where [YYYY-MM-DD] is today's date.
Report structure:
# Pre-Submission Referee Report
**Paper**: [Title]
**Authors**: [Authors]
**Date**: [Today's date]
**Review Standard**: [TARGET_JOURNAL — if top-field, write "Leading Field Journal"; otherwise write the specific journal name]
---
## Overall Assessment
[3–4 sentences synthesized as follows: (1) what the paper does — from Agent 6 Part 1; (2) its principal strength — from Agent 6 Part 1 contribution rating; (3) the single most critical issue — the top CRITICAL item from the Priority Action Items list below. Do not introduce judgments not already present in the agent outputs.]
**Preliminary Recommendation**: [Copy exactly from Agent 6 Part 5 — do not paraphrase]
---
## 1. Contribution & Referee Assessment
[Agent 6 output]
---
## 2. Unsupported Claims & Identification Integrity
[Agent 3 output]
---
## 3. Internal Consistency & Cross-Reference Verification
[Agent 2 output]
---
## 4. Mathematics, Equations & Notation
[Agent 4 output]
---
## 5. Tables, Figures & Documentation
[Agent 5 output]
---
## 6. Spelling, Grammar & Style
[Agent 1 output, preserving its structure]
---
## Priority Action Items
Each agent has tagged its findings as `[CRITICAL]`, `[MAJOR]`, or `[MINOR]`. Collect all tagged items across agents and rank them here using the following triage hierarchy: `[CRITICAL]` items from Agent 3 and Agent 6 Part 2 first, then `[CRITICAL]` from Agent 6 Part 3, then remaining `[CRITICAL]` items by agent order, then all `[MAJOR]` items, then `[MINOR]` items.
**CRITICAL** (must fix — these could cause desk rejection or major referee objections):
1. ...
2. ...
3. ...
**MAJOR** (should fix — will likely be raised by referees):
4. ...
5. ...
6. ...
7. ...
**MINOR** (polish — improves paper quality):
8. ...
9. ...
10. ...
After saving, report to the user:
tools
Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文(用于「文献综述工具选型」与「一键安装/运行」)。
development
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
documentation
Use when the project collects primary data or runs a field, lab, or survey experiment, before the intervention begins — write the pre-analysis plan, size the sample from a power calculation, and register with the AEA RCT Registry. Apply after the design is chosen in aer-identification and before any outcome data are seen.
tools
Guide economists to authoritative data sources with explicit, confirmed data specifications before retrieval; interfaces with Playwright MCP to navigate portals and extract real data, not articles about data.