fcr-review-process
Use to understand how Field Crops Research (FCR) evaluates a manuscript — initial editor screening against the journal's scope boundary, the single-anonymized review model with typically two or more reviewers, and the common reasons for desk rejection (controlled-environment-only, single-site single-season, descriptive/local, out-of-scope species). Sets expectations and shapes the paper to survive review; it does not contact editors.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-review-process --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.
# Review Process (fcr-review-process) Knowing how FCR screens and decides lets you pre-empt the failure modes before submitting. FCR screens **hard against scope** at the editor stage, then uses a **single-anonymized** review with **typically at least two reviewers**. ## When to trigger - Before submitting, to stress-test against desk-rejection grounds - Interpreting a decision letter and setting expectations - Understanding what reviewers and editors weigh in field-crop science ## How FCR review works 1. **Editor scope screening first.** Editors assess suitability before review. The most common **desk-rejection** grounds are scope failures: - **Controlled-environment only** — greenhouse, pots, or any root-restricting system as the main evidence. - **Single site, single season** — not the expected ≥ 2 seasons and/or multiple environments. - **Descriptive / corroborative / local** — no new scientific insight of general relevance. - **Out-of-scope species** — horticultural, woody-perennial, medicinal, or non-cultivated species. - **Inadequate English** or methods too incomplete to evaluate. 2. **Single-anonymized review.** Reviewers know the authors; authors do not know the reviewers
- When to trigger
- How FCR review works
- Shape the paper to pass
- What each gatekeeper weighs
- Worked screening vignette (illustrative)
- Anti-patterns
- Review-risk pass for Field Crops Research
- Output format
- Supplementary resources
What does the fcr-review-process skill do?
Use to understand how Field Crops Research (FCR) evaluates a manuscript — initial editor screening against the journal's scope boundary, the single-anonymized review model with typically two or more reviewers, and the common reasons for desk rejection (controlled-environment-only, single-site single-season, descriptive/local, out-of-scope species). Sets expectations and shapes the paper to survive review; it does not contact editors.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-review-process --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.