fcr-submission
Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter. Final checks; it does not draft content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-submission --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.
# Submission Preflight (fcr-submission) The last check before pressing submit on **Editorial Manager** at `submit.elsevier.com/FIELD`. FCR's most common avoidable failures are **scope mismatch** and **incomplete reporting / declarations**. Check upload-week specifics on the official Elsevier guide before relying on editor names, prices, file prompts, or article-type menus (see `../../resources/official-source-map.md`). ## When to trigger - "Submitting tomorrow" — last pass before upload - Unsure which files/metadata Editorial Manager expects - Confirming scope fit, format, and declarations are complete ## Process facts - **Publisher:** Elsevier (ISSN **0378-4290**). - **Portal:** **Editorial Manager** at `submit.elsevier.com/FIELD`. - **Review model:** **single anonymized** — typically ≥ 2 reviewers. - **Article types:** Original Research Paper · Short Communication · Review (usually invited) · Opinion Paper · Loomis Review (invited). - **Abstract:** **≤ 400 words**. - **Highlights:** **3–5 bullets, each ≤ 85 characters** including spaces. - **Multi-environment rule:** field experiments should span **≥ 2 seasons and/or multiple environments** (unless exceptional circumstances are j
- When to trigger
- Process facts
- Preflight checklist
- Scope & type
- Manuscript & format
- Reporting completeness
- Declarations & files
- Highlights bench-test (illustrative)
- Worked preflight vignette (illustrative)
- Anti-patterns
- Operating pass for Field Crops Research
- Output format
- Supplementary resources
What does the fcr-submission skill do?
Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (<=400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-submission --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.