Use when writing the response to a Conservation Biology revise-and-resubmit. Decisions weigh novelty, transferability, methodological soundness, and direct conservation relevance, so the response must convert each reviewer while keeping the handling editor confident. Structures the response letter; it does not fabricate new results.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill conbio-revision-and-rebuttal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Conbio Revision And Rebuttal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-conbio-revision-and-rebuttal)More formats (shields.io, HTML) on the badges page.
---
name: conbio-revision-and-rebuttal
description: Use when writing the response to a Conservation Biology revise-and-resubmit. Decisions weigh novelty, transferability, methodological soundness, and direct conservation relevance, so the response must convert each reviewer while keeping the handling editor confident. Structures the response letter; it does not fabricate new results.
---
# Revision & Rebuttal (conbio-revision-and-rebuttal)
A *Conservation Biology* revise-and-resubmit is an invitation to convince. Decisions weigh **novelty,
transferability, methodological soundness, and direct conservation relevance**, and the call rests with
the **handling/associate editor**. So the response letter must move *every* reviewer toward yes while
keeping the editor confident the revision is convergent — and the work double-blind throughout.
## When to trigger
- A major/minor revision decision arrived and you are planning the revision + response letter
- Reviewers disagree with each other and you must reconcile their demands
- A reviewer requests analyses that would change the paper's claims or its conservation message
- Writing the cover note to the editor summarizing the revision
## Strategy
1. **Read the editor's letter as the rubric.** The editor signals which points are decisive — often
conservation relevance, soundness, or novelty. Solve those first; the editor adjudicates
disagreements among reviewers.
2. **One point-by-point response, every comment addressed.** Quote each comment, then respond. Never
skip one — silence reads as non-compliance.
3. **Concede or rebut explicitly, with evidence.** For each: did what was asked (say where, with the
new text/table number), or push back **respectfully with a reason** (ecology, design, or evidence).
A well-argued disagreement beats a hollow capitulation that weakens the paper.
4. **Reconcile conflicting reviewers openly.** When one wants the opposite of another, say so, choose a
principled path, and explain the tradeoff to the editor.
5. **Protect the conservation contribution.** Add analyses and caveats that strengthen relevance and
transferability; resist changes that dilute the actionable message or over-claim beyond the design.
6. **Keep double-blind intact** in the revised manuscript, and **update the data/code package** so new
tables/figures remain reproducible and sensitive localities stay masked (see
`conbio-reporting-and-data-policy`).
## Response-letter format
For each reviewer comment:
```
> [Quoted reviewer comment]
Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].
```
Open with a short **summary of the main changes** to the editor; group by reviewer; end each entry with
the location of every change so the editor can verify quickly.
## Anti-patterns
- Ignoring or merging away a comment without a visible response
- Capitulating to a request that breaks the paper's logic or its conservation message
- Defensive or dismissive tone toward reviewers
- "We thank the reviewer" with no actual change or argued reason
- Adding analyses that quietly contradict the original claim without acknowledging it
- Letting the revised manuscript or new exhibits drift out of sync with the deposited package
## Output format
```
【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Conservation message protected】no dilution / over-claim? [Y/N]
【Double-blind + package updated】[Y/N]
【Next】resubmit via ScholarOne Manuscript Central
```
## Supplementary resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — decision categories, reviewer guidelines, double-blind policy
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!