Critiques your paper draft as a skeptical reviewer would. Use when asked to review a paper draft, find weaknesses in a paper, prepare for peer review, anticipate reviewer criticism, or stress-test research before submission. Identifies weak claims, missing baselines, unclear explanations, and overclaims.
Simulates a rigorous peer review to identify weaknesses in your paper draft before submission.
/plugin marketplace add GhostScientist/skills/plugin install ghostscientist-documentation-skills@GhostScientist/skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Channel the energy of the harshest (but fair) reviewer to find weaknesses before your actual reviewers do.
Reviewer 2 is:
Reviewer 2 is NOT:
Read like a busy reviewer would:
First-pass questions:
Go section by section:
Common issues:
Common issues:
Common issues:
Common issues:
Common issues:
Common issues:
These are the questions that sink papers:
Novelty:
Significance:
Soundness:
Clarity:
Rate on standard conference criteria:
| Criterion | Score (1-5) | Justification |
|---|---|---|
| Novelty | How new is this? | |
| Significance | How much does it matter? | |
| Soundness | Is it technically correct? | |
| Clarity | Is it well-written? | |
| Reproducibility | Could I implement this? |
Overall Recommendation:
# Reviewer 2 Report: [Paper Title]
## Summary (2-3 sentences)
[What the paper does and claims]
## Strengths
1. [Strength 1]
2. [Strength 2]
3. [Strength 3]
## Weaknesses
### Major Issues (any one is grounds for rejection)
1. **[Issue Title]**
- What's wrong: [Description]
- Why it matters: [Impact on claims]
- How to fix: [Concrete suggestion]
### Minor Issues (should be fixed but not fatal)
1. **[Issue Title]**
- [Description and suggestion]
### Nitpicks (take or leave)
- [Small thing 1]
- [Small thing 2]
## Questions for Authors
1. [Question that must be answered]
2. [Question that would strengthen paper]
## Missing References
- [Paper 1]: [Why it should be cited]
- [Paper 2]: [Why it should be cited]
## Scores
| Criterion | Score | Notes |
|-----------|-------|-------|
| Novelty | X/5 | |
| Significance | X/5 | |
| Soundness | X/5 | |
| Clarity | X/5 | |
## Overall Assessment
**Recommendation:** [Accept/Reject with confidence]
**In one sentence:** [The core issue or strength]
## Author Rebuttal Priorities
If I were the author, I would address these in order:
1. [Most important thing to address]
2. [Second most important]
3. [Third]
Reviewer 2 is harsh but fair:
Reviewer 2 is NOT:
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.