From science-skills
Triage reviewer comments, prioritize experiments, and draft a point-by-point response letter for Science journal revisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/science-skills:sci-rebuttalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- A decision letter arrives (reject / reject-but-resubmit / major or minor revision).
The editor's framing outranks individual reviewers. Identify:
A "reject but would consider a new submission" is an invitation gated on the deal-breaker. Don't treat it as a flat reject, but don't under-deliver either.
| Bucket | Action |
|---|---|
| Do (fair, feasible) | Make the change; show it; quote the new text/figure. |
| Do-partial | Do what's feasible; explain the boundary with evidence. |
| Defend (wrong/out of scope) | Push back respectfully, with data/citations — not assertion. |
| Defer (future work) | Acknowledge; add a sentence to the text; don't over-promise. |
Most rejections-on-revision come from silently skipping a load-bearing comment or defending when an experiment was actually needed.
For each comment:
Reviewer N, Comment k: <verbatim quote of the reviewer>
Response: <what we did / our reasoning>. <Evidence: new Fig./table, statistics.>
Changes: "<quoted new manuscript text>" (p. X, lines Y–Z; new fig. Sk).
If a reviewer says the conclusion outruns the data, this is the most dangerous comment for a Science paper. Either add the evidence or narrow the claim in the abstract, title, and last paragraph — and say you did. Re-run sci-fit if the narrowed claim weakens broad significance.
Science revisions must preserve a compact, high-signal main story while moving technical detail into the right support surface. Before writing the response, map each requested change onto this packet:
| Science surface | Revision question |
|---|---|
| Main-text claim ladder | Which one or two claims still deserve main-text space after the revision? |
| Figures | Does the new evidence change the main figure logic, not just add another panel? |
| Supplementary materials | Are added methods, controls, statistics, and sensitivity checks easy to find from the response letter? |
| Cross-disciplinary readability | Can a broad Science editor understand why the new evidence changes confidence in the central claim? |
| Scope statement | If the claim narrows, did the abstract, title, first paragraph, and final paragraph all narrow together? |
Do not answer Science reviewers by simply accumulating supplementary analyses. The response must explain how the revision sharpens the main claim, what moved to supplementary materials, and why the core story still has Science-level breadth after any narrowing.
【Decision type】 reject / reject-resubmit / major / minor
【Editor's load-bearing concerns】 [...]
【Deal-breaker】 ... → plan to resolve
【Comment triage】 Do [...] / Do-partial [...] / Defend [...] / Defer [...]
【Experiment priority】 ranked by impact × feasibility
【Claim integrity】 any narrowing needed? (re-check sci-fit)
【Science revision packet】 main-text claim ladder / figures / supplementary materials / scope statement
【Response letter】 drafted point-by-point with quoted changes
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin science-skillsTriage PNAS reviewer comments, prioritize experiments, and draft a point-by-point response letter that is respectful and evidence-led.
Drafts, audits, or revises point-by-point reviewer response letters for Nature-family manuscript revisions. Use when handling reviewer comments, editor decision letters, or revision requests.
Triage Cell journal reviewer comments, prioritize experiments by impact and feasibility, and draft a point-by-point response letter.