Stats
Actions
Tags
From fcr-skills
Runs final pre-submission checks for Field Crops Research via Editorial Manager: article-type, abstract/highlights, agronomic reporting, data-availability, generative-AI declaration, Elsevier formatting, and cover letter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fcr-skills:fcr-submissionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The last check before pressing submit on **Editorial Manager** at `submit.elsevier.com/FIELD`. FCR's
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).
submit.elsevier.com/FIELD.fcr-topic-selection)fcr-figures-and-tables)fcr-cover-letter)Highlights are findings, not topics, and the ≤85-character limit counts spaces. Bench-test each bullet.
| Draft highlight | Chars | Verdict |
|---|---|---|
| "Effects of nitrogen on wheat yield and quality" | 47 | reject — a topic, not a finding |
| "New cultivar raised yield 0.9 t/ha in high-N environments only" | 62 | keep — quantified |
| "G×E explained 38% of yield variance across 8 site-years" | 56 | keep — names the result |
Illustrative dry-run. A maize MET manuscript reaches the final pass: 2 seasons × 4 sites, abstract at 410 words, 6 highlights, a plot-level dataset, but no weather-vs-phenology figure. The preflight catches four blockers: trim the abstract under the 400-word cap; cut highlights to 5 and rewrite topic-style bullets as findings; add the weather-vs-phenology panel so the G×E is interpretable; and draft the data-availability statement to the Mendeley Data DOI. Scope and statistics pass, so once fixed the package is ready for Editorial Manager.
Treat this skill as an executable review pass, not a prose hint. First lock the crop system, environment structure, GxE logic, and yield or physiology endpoint; then judge whether the current manuscript answers the venue's real reader: agronomy reviewers who expect field-based, multi-environment evidence and crop-level general significance.
claim / evidence / risk / manuscript location rows, so the next agent can edit rather than rediscover the issue.resources/official-source-map.md has been checked for upload-week rules and the manuscript has one
concrete fix for the largest venue-specific risk.【Scope & type】field-based + ≥2 seasons/envs + field crop + general; type chosen? [Y/N]
【Abstract & highlights】≤400 words; 3-5 bullets ≤85 chars? [Y/N]
【Reporting complete】cultivar/site/soil/weather-vs-phenology/management/design/stats? [Y/N]
【Declarations】data availability + generative-AI + CRediT/funding? [Y/N]
【Cover letter】scope fit + contribution stated? [Y/N]
【Next】await decision → fcr-revision-and-rebuttal on a revise verdict
../../resources/external_tools.md — reference managers and Elsevier typesetting/templates../../resources/official-source-map.md — official FCR URLs behind every fact in this packnpx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin fcr-skillsRuns a final pre-submission preflight for Agricultural Systems (AgSy) via Elsevier's Editorial Manager: checks article type, abstract ≤250 words, Highlights, graphical abstract, CRediT/declarations, funding/AI disclosures, reference style, and data/code/model availability.
Explains Field Crops Research manuscript review — editor scope screening, single-anonymized review, common desk rejection reasons (controlled-environment-only, single-site-season). Helps shape papers to survive review.
Evaluates manuscript fit for Field Crops Research journal, covering scope, evidence bar, and desk-reject heuristics for agronomy and crop-physiology papers.