Use when writing the cover letter for a Field Crops Research (FCR) submission to the Editors-in-Chief. The letter must establish scope fit (field-based, multi-season/-environment, a field crop, generally significant), state the novel contribution and article type, and confirm originality and data availability. Drafts the letter; it does not contact editors or invent claims.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-cover-letter --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fcr Cover Letter?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-fcr-cover-letter)More formats (shields.io, HTML) on the badges page.
---
name: fcr-cover-letter
description: Use when writing the cover letter for a Field Crops Research (FCR) submission to the Editors-in-Chief. The letter must establish scope fit (field-based, multi-season/-environment, a field crop, generally significant), state the novel contribution and article type, and confirm originality and data availability. Drafts the letter; it does not contact editors or invent claims.
---
# Cover Letter (fcr-cover-letter)
The cover letter is the editor's first scope check. Because FCR has a **strict scope boundary**, the
letter's job is to show — in a few sentences — that the paper is **field-based, multi-environment, on a
field crop, and generally significant**, and to name the **novel contribution** clearly. A vague
letter invites a fast desk rejection.
## When to trigger
- Preparing the submission package and need the cover letter
- Pitching a Review or Opinion proposal to the Editors-in-Chief first
- Explaining why a borderline design (e.g., exceptional single-season circumstances) still fits scope
## What an FCR cover letter must do
1. **Address the Editors-in-Chief** and name the journal and the **article type** (Original Research
Paper / Short Communication / Review / Opinion).
2. **Establish scope fit in one short paragraph.** State that the work is **field-based**, spans
**≥ 2 seasons and/or multiple environments**, concerns a **field crop**, and offers **general
relevance** (not local/descriptive). If a single-season design is unavoidable, justify the
"exceptional circumstances" explicitly.
3. **State the novel contribution.** One or two sentences: what new scientific insight, technology, or
method of general application the paper provides, and the headline **quantitative** result.
4. **Confirm the essentials.** Original work, not under consideration elsewhere; all authors approve;
a **data-availability** position; any **generative-AI** use disclosed; suggested/excluded reviewers
if the journal invites them.
5. **Be brief and specific.** Roughly one page; no hype; let the agronomic significance speak.
## Skeleton
```
Dear Editors-in-Chief,
We submit "[Title]" for consideration as an [article type] in Field Crops Research.
[Scope + contribution: field-based study across N seasons and M environments on
<field crop>; the novel finding is ___, quantified as ___; it matters generally
because ___.]
The work is original and not under consideration elsewhere; all authors approve
submission. Data availability: [shared in <repository> / restricted because ___].
[We did/did not use generative-AI tools, disclosed in the manuscript.]
[Optional: suggested reviewers / conflicts.]
Sincerely, [Corresponding author, affiliation, contact]
```
## Anti-patterns
- A letter that summarises the abstract but never states **scope fit**
- Claiming novelty without the quantitative finding or its general relevance
- Hiding a single-site/single-season limitation instead of justifying it
- Overstating impact; emotional or boilerplate appeals
- Forgetting originality, data-availability, or AI-disclosure statements
## Output format
```
【Article type】named? [Y/N]
【Scope fit stated】field-based + ≥2 seasons/envs + field crop + general? [Y/N]
【Contribution】novel insight + headline quantitative result stated? [Y/N]
【Declarations】originality + data availability + AI disclosure? [Y/N]
【Length/tone】~1 page, specific, no hype? [Y/N]
【Next】fcr-review-process
```
## Supplementary resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — scope boundary, article types, and submission expectations
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!