Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Fcr Experimental Design

ASecurity

Use when designing or defending the field-experiment or modelling design of a Field Crops Research (FCR) manuscript — multi-environment trials, randomization and replication, blocking and split-plot layouts, genotype-by-environment (G×E) structure, and crop-model calibration/validation. FCR expects field experiments to span at least two seasons and/or multiple environments. Strengthens the design; it does not write code.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-experimental-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fcr Experimental Design?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Fcr Experimental Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-fcr-experimental-design/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-fcr-experimental-design)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: fcr-experimental-design
description: Use when designing or defending the field-experiment or modelling design of a Field Crops Research (FCR) manuscript — multi-environment trials, randomization and replication, blocking and split-plot layouts, genotype-by-environment (G×E) structure, and crop-model calibration/validation. FCR expects field experiments to span at least two seasons and/or multiple environments. Strengthens the design; it does not write code.
---

# Experimental Design (fcr-experimental-design)

FCR is demanding about **field-experimental rigour**. The design must credibly connect the agronomic
question to evidence that generalises across environments. The single most important FCR-specific rule:
field experiments should, unless exceptional circumstances apply, span **at least two seasons and/or
multiple locations/environments**. Design for that from the start.

## When to trigger

- Planning a multi-environment trial (MET) or a season×site×treatment layout
- A reviewer questioned randomization, replication, blocking, or G×E inference
- Deciding how to characterise environments (soil, weather, phenology)
- Designing a crop-modelling study (calibration/validation, scenario design)

## Field-experiment design essentials

- **Multi-environment by design.** Plan ≥ 2 seasons and/or multiple sites; define what an
  "environment" is (site×year, managed water/N regime). State why the set spans the target population
  of environments.
- **Randomization & replication.** Use a proper randomized design (RCBD, **resolvable
  incomplete-block / alpha-lattice**, split-plot for factor hierarchies, strip-plot, augmented for many
  genotypes). State replication per environment and the randomization procedure — not "plots were
  arranged."
- **Blocking & spatial control.** Block against known field gradients; plan for **spatial analysis**
  (e.g., row/column or P-spline) where fields are large or heterogeneous.
- **Plot management detail.** Plot size, borders/guard rows, sowing density, dates, and the management
  applied — enough to reproduce the experiment.
- **Environment characterisation.** Record **soil and weather** and present weather **in relation to
  crop phenology**; this is what lets readers interpret G×E.

## Genotype/treatment × environment (G×E)

- Decide up front how G×E will be modelled: factorial structure, which effects are **fixed vs.
  random**, and how environments enter (random sample vs. fixed targets).
- Plan stability/adaptation analyses (Finlay–Wilkinson regression, **AMMI**, **GGE biplot**) where
  ranking across environments is the question.

## Crop-modelling design

- State the model and **version**, the **cultivar coefficients**, and the **calibration vs.
  validation** split (independent data, not the same trials).
- Justify the scenario/factor design and the environments simulated; report what the model **adds**
  beyond the field data (extrapolation, yield-gap decomposition, generalisation).

## The generalisation test (FCR-specific)

For your design, write one sentence: *"These environments represent ___, so the result is expected to
hold for ___ (and not for ___)."* If you cannot, the design does not yet support a general,
FCR-worthy claim — add environments or scope the claim.

## Anti-patterns

- One site, one season presented as sufficient (fails the multi-environment expectation)
- "Randomized" asserted with no design named, no replication count, no layout
- Treating a controlled-environment study as the main evidence (out of scope — see `fcr-topic-selection`)
- Ignoring spatial heterogeneity in large fields; pseudoreplication (sub-samples treated as reps)
- Calibrating and validating a model on the same data

## Output format

```
【Design】RCBD / alpha-lattice / split-plot / MET / modelling
【Environments】#seasons × #sites; what they represent
【Randomization & replication】procedure + reps per environment
【G×E plan】fixed/random structure; stability analysis if relevant
【Environment characterisation】soil + weather vs. phenology recorded? [Y/N]
【Generalisation sentence】represents ___ → holds for ___
【Next】fcr-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — design packages (agricolae, FielDHub) and crop models (APSIM, DSSAT, STICS)
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — the ≥2-seasons/-environments rule and reproducibility expectations

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →