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 Review Process

ASecurity

Use to understand how Field Crops Research (FCR) evaluates a manuscript — initial editor screening against the journal's scope boundary, the single-anonymized review model with typically two or more reviewers, and the common reasons for desk rejection (controlled-environment-only, single-site single-season, descriptive/local, out-of-scope species). Sets expectations and shapes the paper to survive review; it does not contact editors.

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-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fcr Review Process?

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

Security grade badge for Fcr Review Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-fcr-review-process/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-fcr-review-process)

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

Download with Pro
Files
SKILL.md
---
name: fcr-review-process
description: Use to understand how Field Crops Research (FCR) evaluates a manuscript — initial editor screening against the journal's scope boundary, the single-anonymized review model with typically two or more reviewers, and the common reasons for desk rejection (controlled-environment-only, single-site single-season, descriptive/local, out-of-scope species). Sets expectations and shapes the paper to survive review; it does not contact editors.
---

# Review Process (fcr-review-process)

Knowing how FCR screens and decides lets you pre-empt the failure modes before submitting. FCR screens
**hard against scope** at the editor stage, then uses a **single-anonymized** review with **typically
at least two reviewers**.

## When to trigger

- Before submitting, to stress-test against desk-rejection grounds
- Interpreting a decision letter and setting expectations
- Understanding what reviewers and editors weigh in field-crop science

## How FCR review works

1. **Editor scope screening first.** Editors assess suitability before review. The most common
   **desk-rejection** grounds are scope failures:
   - **Controlled-environment only** — greenhouse, pots, or any root-restricting system as the main evidence.
   - **Single site, single season** — not the expected ≥ 2 seasons and/or multiple environments.
   - **Descriptive / corroborative / local** — no new scientific insight of general relevance.
   - **Out-of-scope species** — horticultural, woody-perennial, medicinal, or non-cultivated species.
   - **Inadequate English** or methods too incomplete to evaluate.
2. **Single-anonymized review.** Reviewers know the authors; authors do not know the reviewers.
   Suitable papers are sent to **typically two or more** expert reviewers.
3. **Decision categories.** Reject / major revision / minor revision / accept (exact labels per
   Editorial Manager). Revisions are common; address every point.
4. **Co-submission.** Related data/methods may be routed to **Data in Brief** / **MethodsX**.

## Shape the paper to pass

- Make **scope fit obvious** in the cover letter, abstract, and introduction (field-based,
  multi-environment, field crop, general relevance).
- State the **novel contribution** and link results to **yield / biophysical process**.
- Use **statistics that match the design** (mixed models, G×E) so a methods reviewer is satisfied.
- Report enough agronomic detail (soil, weather-vs-phenology, management) to be reproducible.
- Make the **discussion interpret**, not repeat — a frequent reviewer complaint.

## Anti-patterns

- Submitting controlled-environment-only or single-site/single-season work to a multi-environment journal
- A descriptive "we measured X here" paper with no general insight
- Wrong error structure or pseudoreplication that a methods reviewer will catch
- A discussion that restates results without agronomic interpretation
- Conclusions not justified by the data

## Output format

```
【Scope screen】field-based? ≥2 seasons/envs? field crop? general? — any red flags?
【Novelty】new insight of general relevance stated? [Y/N]
【Statistics】design-appropriate (mixed model / G×E)? [Y/N]
【Reproducibility】agronomic detail + data availability ready? [Y/N]
【Realistic outcome】reject / major / minor revision / accept
【Next】fcr-submission (or fcr-revision-and-rebuttal once decided)
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model, reviewer count, scope-based desk-rejection grounds

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 →