
Paper Rebuttal
You've got reviewer feedback and need to write a rebuttal that actually moves scores. This walks you through the non-obvious parts: color-coding comments by impact (red for score-drivers, gray for minor fixes), identifying your champion reviewer and arming them with copy-pasteable arguments, and spending your word budget where it matters (60% on red issues, not equal time on everything). The counterintuitive bits are worth the read. Concede something small to win credibility on big points. One new experiment beats three paragraphs of explanation. Your real audience isn't the negative reviewer, it's the positive one who'll argue for you in the AC discussion. Includes response templates and strategies for "limited novelty" and other common attacks.
- skills.sh installs
- 453
- GitHub stars
- 488
- last updated
- Aug 21, 2026
Install
$ npx -y skills add evoscientist/evoskills --skill paper-rebuttal --agent claude-codeInstalls into .claude/skills of the current project.
Files
Paper Rebuttal
A systematic approach to writing rebuttals after receiving peer review feedback. The goal is not to defend every point — it's to move scores by addressing the concerns that actually drive them.
When to Use This Skill
- User received reviewer comments and needs to write a rebuttal
- User asks how to respond to specific reviewer criticism
- User wants to analyze reviews strategically before responding
- User mentions "rebuttal", "reviewer comments", "review feedback", "respond to reviewers"
For pre-submission self-review and catching weaknesses before they become reviewer complaints, use the
paper-reviewskill.
Step 1: Diagnose Reviews
Before writing a single word, answer: "Why did this reviewer give this exact score?" Not what they wrote — what drove the score. Most researchers skip this and address every comment equally. That is a mistake.
Score Diagnosis
For each reviewer, ask: "What would move this reviewer from their current score to acceptance?"
Sponsors
Details
- Repository
- github.com/evoscientist/evoskills
- Categories
- Git & Pull Requests, Documentation, Code Review & Quality, Design & UI/UX
- First seen
- Jun 3, 2026