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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-revision-and-rebuttal --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ## Strategy 1. **Read the editor's letter as the rubric.** The editor signals the decisive points; solve those first. The editor adjudicates disagreements among reviewers. 2. **Point-by-point, 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/figure number), or push back **respectfully with a reason** (design, agronomy, or data). A well-argued disagreemen
- When to trigger
- Strategy
- Common FCR reviewer asks (anticipate them)
- Response-letter format
- Referee-pushback playbook (FCR-specific fixes)
- Worked rebuttal vignette (illustrative)
- Anti-patterns
- Output format
- Supplementary resources
What does the fcr-revision-and-rebuttal skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-revision-and-rebuttal --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.