brycewang-stanford/Auto-Empirical-Research-Skills / skills/24-Imbad0202-academic-research-skills/academic-paper-reviewer
academic-paper-reviewer
VerifiedMulti-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, and Socratic guided modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.4 KB |
| agents/devils_advocate_reviewer_agent.md | markdown | 8.2 KB |
| agents/domain_reviewer_agent.md | markdown | 8.7 KB |
| agents/editorial_synthesizer_agent.md | markdown | 10.8 KB |
| agents/eic_agent.md | markdown | 5.4 KB |
| agents/field_analyst_agent.md | markdown | 9.1 KB |
| agents/methodology_reviewer_agent.md | markdown | 10.1 KB |
| agents/perspective_reviewer_agent.md | markdown | 11.2 KB |
| examples/hei_paper_review_example.md | markdown | 25.8 KB |
| examples/interdisciplinary_review_example.md | markdown | 18.7 KB |
| references/editorial_decision_standards.md | markdown | 9.0 KB |
| references/quality_rubrics.md | markdown | 6.7 KB |
| references/review_criteria_framework.md | markdown | 9.9 KB |
| references/statistical_reporting_standards.md | markdown | 22.2 KB |
| references/top_journals_by_field.md | markdown | 12.2 KB |
| templates/editorial_decision_template.md | markdown | 6.3 KB |
| templates/peer_review_report_template.md | markdown | 7.3 KB |
| templates/revision_response_template.md | markdown | 6.9 KB |
templates/peer_review_report_template.md
View on GitHub# Peer Review Report Template
This template is used by all reviewer agents (EIC, Reviewers 1-3). Each reviewer uses the same structure but fills in review content from their respective perspectives.
---
## Usage Instructions
1. Text in `[brackets]` is explanatory and needs to be replaced with actual content
2. Each reviewer must fully complete all required fields (items marked with *)
3. Detailed Comments are section-by-section commentary; only comment on sections relevant to your review focus
4. Language follows the paper's language (Chinese papers reviewed in Chinese, English papers in English)
---
## Template
```markdown
# Peer Review Report
## Manuscript Information
- **Title**: [Paper title]
- **Manuscript ID**: [If available, enter manuscript ID]
- **Review Date**: [Review date]
- **Review Round**: [Round N review]
---
## Reviewer Information
### Reviewer Role *
[EIC / Peer Reviewer 1 (Methodology) / Peer Reviewer 2 (Domain) / Peer Reviewer 3 (Perspective)]
### Reviewer Identity *
[Identity description configured by field_analyst_agent]
### Review Focus *
[Core focus of this review, 2-3 sentences]
---
## Overall Assessment *
### Recommendation *
[Select one]
- [ ] **Accept** — Can be published directly, only minor formatting changes needed
- [ ] **Minor Revision** — Minor revisions needed, no re-review after revision
- [ ] **Major Revision** — Substantial revisions needed, re-review required after revision
- [ ] **Reject** — Not suitable for publication in this journal
### Confidence Score *
[1-5]
| Score | Meaning |
|-------|---------|
| 5 | Completely within my area of expertise, I am very confident in my assessment |
| 4 | Mostly within my area of expertise, high confidence |
| 3 | Partially within my area of expertise, moderate confidence |
| 2 | Some aspects outside my expertise, somewhat uncertain about my assessment |
| 1 | Mostly outside my expertise, my opinion is for reference only |
### Summary Assessment *
[150-250 word overall assessment]
Requirements:
- Sentences 1-2: What the paper does (topic, methods, main findings)
- Sentences 3-4: Overall quality assessment (from your review focus perspective)
- Sentences 5-6: Most critical strengths and weaknesses
- Final: Your recommendation rationale
---
## Strengths *
List 3-5 strengths of the paper. Each must:
- Have a specific title
- Cite passages, data, or page numbers from the paper
- Explain why it is a strength
### S1: [Strength title] *
[Specific description. E.g., "The research design uses a quasi-experimental pretest-posttest control group design (p. X), effectively controlling for..."]
### S2: [Strength title] *
[Specific description]
### S3: [Strength title] *
[Specific description]
### S4: [Strength title]
[Optional]
### S5: [Strength title]
[Optional]
---
## Weaknesses *
List 3-5 weaknesses of the paper. Each must:
- Have a specific title
- Describe the specific problem
- Explain why it is a problem
- Provide specific improvement suggestions
### W1: [Weakness title] *
**Problem**: [Specific description of the problem, citing paper passages]
**Why it matters**: [Explain the impact of this problem]
**Suggestion**: [Specific improvement direction]
**Severity**: [Critical / Major / Minor]
### W2: [Weakness title] *
**Problem**: [...]
**Why it matters**: [...]
**Suggestion**: [...]
**Severity**: [Critical / Major / Minor]
### W3: [Weakness title] *
**Problem**: [...]
**Why it matters**: [...]
**Suggestion**: [...]
**Severity**: [Critical / Major / Minor]
### W4: [Weakness title]
[Optional, same format as above]
### W5: [Weakness title]
[Optional, same format as above]
---
## Detailed Comments *
Section-by-section commentary on the paper. Only comment on sections relevant to your review focus.
### Title & Abstract
- [Assess title accuracy and appeal]
- [Assess abstract structure and completeness]
### Introduction
- [Is research background sufficient]
- [Is research question/purpose clear]
- [Is research motivation persuasive]
### Literature Review / Theoretical Framework
- [Literature coverage] (Primarily reviewed by Reviewer 2)
- [Theoretical framework appropriateness] (Primarily reviewed by Reviewer 2)
- [Research gap argument]
### Methodology / Research Design
- [Research design appropriateness] (Primarily reviewed by Reviewer 1)
- [Sampling strategy]
- [Data collection]
- [Analysis methods]
### Results / Findings
- [Completeness of results presentation]
- [Figure/table quality]
- [Alignment of results with research questions]
### Discussion
- [Whether discussion addresses research questions]
- [Dialogue with the literature]
- [Theoretical and practical implications]
- [Discussion of limitations]
### Conclusion
- [Whether conclusions over-infer]
- [Value of future research directions]
### References
- [Citation format]
- [Quality and recency of cited references]
---
## Questions for Authors *
List 2-4 questions requiring author response. These questions should:
- Not be rhetorical, but genuinely need answering
- The answer could change the paper's quality or direction
- Be specific and answerable
1. [Question 1]
2. [Question 2]
3. [Question 3] (Optional)
4. [Question 4] (Optional)
---
## Minor Issues
List minor issues that don't affect academic quality but need correction.
### Language / Grammar
- [Page X, Line Y: Specific language issue]
- [...]
### Citation Format
- [Specific citation format issues]
- [...]
### Figures and Tables
- [Figure/table improvement suggestions]
- [...]
### Layout
- [Layout issues]
- [...]
---
## Dimension Scores *
Score each dimension 0-100 using the rubrics in `references/quality_rubrics.md`. Report the range descriptor that best matches.
| Dimension | Score (0-100) | Descriptor | Notes |
|-----------|--------------|------------|-------|
| Originality (20%) | | [Exceptional/Strong/Adequate/Weak/Insufficient] | |
| Methodological Rigor (25%) | | [Exceptional/Strong/Adequate/Weak/Insufficient] | |
| Evidence Sufficiency (25%) | | [Exceptional/Strong/Adequate/Weak/Insufficient] | |
| Argument Coherence (15%) | | [Exceptional/Strong/Adequate/Weak/Insufficient] | |
| Writing Quality (15%) | | [Exceptional/Strong/Adequate/Weak/Insufficient] | |
| Literature Integration (optional) | | [See rubrics] | R2 focus |
| Significance & Impact (optional) | | [See rubrics] | R3 focus |
| **Weighted Average** | | **[Accept/Minor/Major/Reject]** | |
```
---
## Format Guidelines
### Severity Levels
| Level | Definition | Revision Requirement |
|-------|-----------|---------------------|
| **Critical** | Cannot be accepted without fixing | Required Revision |
| **Major** | Significantly affects paper quality | Strongly Recommended |
| **Minor** | Better if fixed, acceptable if not | Suggested |
### How to Cite Paper Passages
```
# Correct
"The author states on p. 12: 'AI can replace human judgment in QA processes,' but..."
# Correct
"The data in Table 3 shows p = 0.04, but the author does not report effect sizes..."
# Incorrect (too vague)
"Methodology has problems"
"Literature review is not comprehensive enough"
```
### Constructive Tone Examples
```
# Good
"The author is encouraged to consider adding X analysis to strengthen the argument for Y."
# Good
"This section's argumentation could be clearer. Specifically, the causal inference in paragraph 2, page 8 needs additional evidence support."
# Bad
"The author clearly does not understand X."
# Bad
"This method is wrong."
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |