Agent skill · Code Review & Quality

fcr-workflow

Use as the entry point for any Field Crops Research (FCR) manuscript. Routes to the right FCR sub-skill based on where you are in the lifecycle and which article type (Original Research Paper, Review, Short Communication, Opinion, Loomis Review) fits. It checks scope-fit first — FCR rejects controlled-environment-only and single-site single-season work — then dispatches; it does not draft content.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-workflow --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Field-Crops-Research-Skills/skills/fcr-workflow/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# FCR Workflow Router (fcr-workflow) The orchestrator for a Field Crops Research submission. Figure out the stage and the **article type**, then send the user to the matching skill. FCR is an **empirical field-agronomy** journal — the router's first job is a **scope gate**: is this genuine field-based research with **multi-season and/or multi-environment** relevance? If not, fix that before anything else. ## When to trigger - Starting a new FCR paper and unsure where to begin - Mid-project and unsure which skill applies next - Deciding which **article type** fits the work - Returning with a decision letter (route to `fcr-revision-and-rebuttal`) ## Scope gate (ask first, every time) | Question | If "no" | |----------|---------| | Is it **field-based** (not greenhouse/pot/root-restricting only)? | Likely out of scope → `fcr-topic-selection` | | Does it have **≥ 2 seasons and/or multiple environments**? | Redesign or reframe → `fcr-experimental-design` | | Is the crop a **field crop** (not horticultural/woody-perennial/non-cultivated)? | Out of scope → `fcr-topic-selection` | | Is it more than **corroborative / descriptive / local**? | Sharpen the contribution → `fcr-topic-selection`

What's inside
Steps it walks through
  1. When to trigger
  2. Scope gate (ask first, every time)
  3. First question: which article type?
  4. Routing map (stage → skill)
  5. Default order
  6. Desk-reject triage table (route before you draft)
  7. Worked routing vignette (illustrative)
  8. Anti-patterns
  9. Output format
  10. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the fcr-workflow skill do?

Use as the entry point for any Field Crops Research (FCR) manuscript. Routes to the right FCR sub-skill based on where you are in the lifecycle and which article type (Original Research Paper, Review, Short Communication, Opinion, Loomis Review) fits. It checks scope-fit first — FCR rejects controlled-environment-only and single-site single-season work — then dispatches; it does not draft content.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-workflow --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.

Keep going