Menu

Individual skill

rebuttal-and-response-to-reviewers

Plan and write responses to peer review, including journal "response to reviewers" letters for revise-and-resubmit, conference rebuttals under strict length limits (OpenReview/ICLR, NeurIPS, ICML, ACL ARR, CVPR), author responses to meta-reviews, and appeals. Use when a user receives reviews, must triage reviewer comments, draft point-by-point replies, decide what new experiments to run, disagree respectfully with a reviewer, or track manuscript changes for a revision. For authors answering reviews of their own manuscript; to write a review of someone else's paper, use peer-review instead.

plugins/KalarisLabs/research-agent-skills/skills/rebuttal-and-response-to-reviewers/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Declared tags are partial or unavailable.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Responding to Reviewers

The audience of a response is the **editor or area chair**, who must decide
quickly whether concerns were addressed. Make every reply easy to verify:
quote the concern, answer it directly, show the change with a location.

## Step 1: Triage (before writing anything)

Split every review into atomic comments and classify each in a table:

| ID | Reviewer | Comment (short) | Type | Effort | Plan |
|---|---|---|---|---|---|
| R1.1 | 1 | Missing baseline X | Experiment | High | Run X on 2 datasets |
| R2.3 | 2 | Claim in §4 overstated | Wording | Low | Soften + add limitation |