Individual skill

fcr-revision-and-rebuttal

Use when writing the response to a Field Crops Research (FCR) revision decision (major or minor) and revising the manuscript. FCR reviewers commonly press on scope/generality, statistics and G×E, reproducibility detail, and a discussion that interprets rather than repeats. The response must address every point while protecting the contribution. Structures the response letter; it does not fabricate new results.

Field-Crops-Research-Skills/skills/fcr-revision-and-rebuttal/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 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,405
Repository last updated
Sep 27, 2026
License
MIT

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

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

# Revision & Rebuttal (fcr-revision-and-rebuttal)

An FCR **revise** decision is an opportunity, not a formality. The response letter must move **every
reviewer** toward acceptance while keeping the editor confident the revision converges. FCR reviewers
tend to focus on a recurring set of agronomy concerns — answer them with **data and detail**, not
assertion.

## When to trigger

- A major- or minor-revision decision arrived and you are planning the response
- Reviewers disagree and you must reconcile their requests
- A reviewer wants additional environments, statistics, or reproducibility detail
- Writing the cover note to the editor summarising the revision
Back to top