fcr-reporting-and-data-policy
Use when preparing the reporting completeness and research-data materials for a Field Crops Research (FCR) manuscript. FCR requires a data-availability statement at submission, full agronomic reporting (cultivar, soil, weather vs. phenology, management, design), declaration of any generative-AI use, and supports data/methods co-submission to Data in Brief / MethodsX. Prepares the materials; it does not waive requirements.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-reporting-and-data-policy --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.
# Reporting & Data Policy (fcr-reporting-and-data-policy) FCR does not just want results — it wants the **agronomic context** that makes them interpretable and reproducible, plus a **statement of data availability at submission**. Build these as you go so they do not stall the submission. ## When to trigger - Assembling the methods section for completeness before submission - Writing the **data-availability statement** required at submission - Deciding whether to co-submit a dataset/method to **Data in Brief** / **MethodsX** - Disclosing any **use of generative AI** in preparing the manuscript ## Reporting completeness (FCR-specific) A field-crop paper is reproducible only if the methods report all of: - [ ] **Crop & cultivar(s)** and, where relevant, maturity group / genotype identity - [ ] **Site(s) & seasons** with coordinates; the environments and what they represent - [ ] **Soil** properties (type, texture, relevant chemistry) for each site - [ ] **Weather** (radiation, temperature, rainfall) shown **in relation to crop phenology** - [ ] **Management**: sowing date/density, fertilisation, irrigation, crop protection, tillage - [ ] **Experimental design**: layout, randomization
- When to trigger
- Reporting completeness (FCR-specific)
- Data availability (state it at submission)
- Other declarations
- Minimum agronomic metadata table (what an FCR methods reviewer audits)
- Worked data-availability vignette (illustrative)
- Anti-patterns
- Output format
- Supplementary resources
What does the fcr-reporting-and-data-policy skill do?
Use when preparing the reporting completeness and research-data materials for a Field Crops Research (FCR) manuscript. FCR requires a data-availability statement at submission, full agronomic reporting (cultivar, soil, weather vs. phenology, management, design), declaration of any generative-AI use, and supports data/methods co-submission to Data in Brief / MethodsX. Prepares the materials; it does not waive requirements.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-reporting-and-data-policy --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.