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 Workflow

ASecurity

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.

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-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fcr Workflow?

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

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

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

Download with Pro
Files
SKILL.md
---
name: fcr-workflow
description: 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.
---

# 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` |

## First question: which article type?

| Situation | Article type | Route to |
|-----------|--------------|----------|
| Full original field/modelling study | **Original Research Paper** | normal pipeline below |
| Concise, complete, focused study | **Short Communication** | normal pipeline, tighter scope |
| Critical synthesis of a topic | **Review** (usually invited; propose first) | `fcr-literature-positioning` + `fcr-topic-selection` |
| Perspective / position piece | **Opinion Paper** | `fcr-topic-selection` + `fcr-writing-style` |
| Invited major review | **Loomis Review** (by invitation) | `fcr-literature-positioning` |

## Routing map (stage → skill)

```text
Idea / scope fit?               → fcr-topic-selection
Where does it sit in the field? → fcr-literature-positioning
Is the design defensible?       → fcr-experimental-design
Are the analyses sound?         → fcr-data-analysis
Are the exhibits clear?         → fcr-figures-and-tables
Data availability & reporting?  → fcr-reporting-and-data-policy
Does it read for agronomists?   → fcr-writing-style
Need a cover letter?            → fcr-cover-letter
How will it be judged?          → fcr-review-process
Ready to submit?                → fcr-submission
Got a decision / revision?      → fcr-revision-and-rebuttal
```

## Default order

`topic-selection → literature-positioning → experimental-design → data-analysis → figures-and-tables →
reporting-and-data-policy → writing-style → cover-letter → review-process → submission →
revision-and-rebuttal`

Iterate: most papers loop design ↔ analysis ↔ figures several times before writing-style.

## Anti-patterns

- Skipping the scope gate and investing in controlled-environment-only or single-site data
- Treating one season at one site as enough (FCR expects multi-season/-environment relevance)
- Forcing a Review/Opinion frame onto what is really an Original Research Paper
- Leaving the data-availability statement and highlights to the last minute

## Output format

```
【Scope gate】field-based? multi-environment? field crop? more than local? [pass/fix]
【Stage】idea / positioning / design / analysis / exhibits / reporting / writing / cover / review / submit / revise
【Article type】Original Research / Short Communication / Review / Opinion / Loomis Review
【Route to】fcr-<skill>
【Why】one line
【Then】the next skill after that
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — agronomy data + software by method
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — official FCR URLs behind every fact in this pack

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 →