rebuttal

Convert reviewer feedback into experiments, manuscript revisions, and a structured rebuttal response package.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill rebuttal-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rebuttal
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/skills/deepscientist-rebuttal
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill rebuttal-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Responding to peer review requires turning scattered reviewer comments into a coordinated set of experiments, text changes, and honest reply letters, which is easy to do inconsistently or dishonestly under deadline pressure. ## Core Features & Use Cases - Review Normalization: Parses reviewer comments, meta-reviews, and decision letters into a stable atomic review matrix with ids like R1-C1, classifying each item as editorial, text-only, evidence gap, experiment gap, claim scope, or unaddressable. - Routed Action Planning: Decides per item whether the right response is text revision, evidence repackaging, literature positioning, baseline recovery, supplementary experiments, claim downgrade, or an explicit limitation, then routes experiments to analysis campaigns and edits to the writing workflow. - Evidence-Backed Response Letter: Assembles a point-by-point response letter, text deltas, and evidence update notes using templates, with strict rules against inventing results or overpromising. - Use Case: A researcher receives three reviewer reports demanding extra baselines and narrower claims; the skill builds the review matrix, launches only the genuinely needed supplementary experiments tied to named reviewer items, revises the manuscript scope, and drafts the rebuttal letter. ## Quick Start Use the rebuttal skill to organize these reviewer comments into an action plan and draft a point-by-point response letter for my paper.

Frequently Asked Questions about rebuttal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a rebuttal response to peer reviewers?▼

Start by normalizing reviewer comments into atomic items with stable ids, classify each as editorial, text-only, evidence gap, or experiment gap, then draft point-by-point replies that answer each concern directly with evidence and manuscript changes. Templates for the review matrix, action plan, and response letter guide the structure.

How to decide which reviewer comments need new experiments?▼

Classify each comment first: wording gaps, literature positioning issues, and evidence-presentation gaps rarely need new runs. Only genuine experiment gaps or missing baselines justify supplementary experiments, and each run must map to a named reviewer item with a hypothesis and minimal success criterion.

Can I respond to a reviewer without running the requested experiment?▼

Yes, when the request is infeasible or out of scope, classify it as cannot_fully_address and state the honest limitation explicitly in the response letter. Never pretend a limitation is solved by reframing it, and never promise future work unless the format allows it.

What should a point-by-point response letter include?▼

Include a brief cover note, an overall response summarizing the revision strategy, strengths recognized across reviewers, and per-item replies that restate the reviewer wording, answer directly in one to two paragraphs, and list what changed in experiments, figures, text, or claim scope.

When should I downgrade a claim during revision?▼

Downgrade a claim when new evidence no longer supports its original scope or a reviewer challenge cannot be fully answered. Record the narrowing in text deltas, revise the outline before polishing prose, and state the remaining limitation explicitly in the response letter.