> Prepare a paper for peer review. Reads the paper and experiment results, selects the strongest ablations, anticipates reviewer questions, finds weaknesses before submission, and drafts rebuttals to actual reviews. Use when the user asks about "reviewer questions", "anticipate reviewers", "rebuttal", "paper weaknesses", "defend the paper", "strengthen the paper", "select the strongest ablations", "fortify the paper", or "prepare for peer review".
npx skills add https://github.com/fcakyon/labrat --skill rebuttal
Venue: $ARGUMENTS
Discover the paper, result and config files as in Step 1 (Discover Files) of /labrat:paper-check, including wandb logs and checkpoint directories. Then list the paper's claims (contributions and experiments), its metrics and baselines, and every available run and its outcome, including the ablation variants the configs define.
Identify weaknesses from a reviewer's perspective:
If a venue was given, use its matching entry below.
Top-tier ML/CV conferences (CVPR, NeurIPS, ICLR, ECCV):
Workshops:
Journals:
List the 10 most likely reviewer questions, most likely first, phrased as a reviewer would write them, in this form:
Q: [Reviewer question]
Motivation: [Why this would be asked]
Answerable: [Yes, cite Table X / No, would need experiment Y]
Draft response: [If answerable, 2-3 sentences]
Take each delta from Ablation analysis in /labrat:compare (same-step, interaction-checked), then rank:
| Run | Factor Changed | Primary Metric Delta | Narrative Strength | Include? |
|-----|---------------|--------------------|--------------------|----------|
Ranking criteria:
Recommend: main paper (top 3-5) vs supplementary (rest).
Frame negative results as analysis, not failure ("We explored X but found it did not improve over Y because Z"), and put them in the supplementary if they do not fit the main paper.
If responding to actual reviews:
Rebuttal structure per reviewer:
We thank Reviewer X for their thoughtful feedback.
**[Major concern]**: [Direct response with evidence]
**[Specific question]**: [Concrete answer]
**[Suggestion]**: [How we will incorporate it]
## Rebuttal Report
### Weaknesses
[Table of categorized weaknesses with severity, prioritized]
### Recommended Ablation Subset
[Table with justification for each]
### Top 10 Anticipated Questions
[Numbered list with answerability and draft responses]
### Suggested Edits
[Specific paragraph-level improvements to strengthen before submission]
Add the per-reviewer rebuttal drafts from Step 7 when responding to actual reviews.
Take fcakyon/rebuttal from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.