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 Submission

ASecurity

Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (~400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter. Final checks; it does not draft content.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Fcr Submission?

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

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

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

Download with Pro
Files
SKILL.md
---
name: fcr-submission
description: Use when running the final pre-submission preflight for Field Crops Research (FCR) via Editorial Manager — article-type selection, abstract (~400 words) and highlights (3-5 bullets of <=85 characters), complete agronomic reporting, data-availability statement, generative-AI declaration, Elsevier formatting, and the cover letter. Final checks; it does not draft content.
---

# Submission Preflight (fcr-submission)

The last check before pressing submit on **Editorial Manager**. FCR's most common avoidable failures
are **scope mismatch** and **incomplete reporting / declarations**. Verify volatile specifics on the
official Elsevier guide before relying on them (live page may 403 to automated tools — see
`../../resources/official-source-map.md`).

## When to trigger

- "Submitting tomorrow" — last pass before upload
- Unsure which files/metadata Editorial Manager expects
- Confirming scope fit, format, and declarations are complete

## Process facts (verify volatile items on the official page)

- **Publisher:** Elsevier (ISSN **0378-4290**).
- **Portal:** **Editorial Manager** (confirm current URL on the live guide).
- **Review model:** **single anonymized** — typically ≥ 2 reviewers.
- **Article types:** Original Research Paper · Short Communication · Review (usually invited) · Opinion
  Paper · Loomis Review (invited).
- **Abstract:** **≤ ~400 words** (待核实 exact cap).
- **Highlights:** **3–5 bullets, each ≤ 85 characters** including spaces.
- **Multi-environment rule:** field experiments should span **≥ 2 seasons and/or multiple
  environments** (unless exceptional circumstances are justified).
- **Data availability:** must be **stated at submission**.
- **Generative AI:** **declare any use** in manuscript preparation.

## Preflight checklist

### Scope & type
- [ ] Field-based, multi-season/-environment, a field crop, generally significant (see `fcr-topic-selection`)
- [ ] Article type chosen; Review/Opinion proposal cleared with editors if required

### Manuscript & format
- [ ] Abstract ≤ ~400 words; states purpose, environments, quantitative result, conclusion
- [ ] **3–5 highlights**, each ≤ 85 characters, findings not topics
- [ ] Structure: focused intro → complete methods → concise results → interpretive discussion
- [ ] SI units; consistent Elsevier/FCR reference style; grammatically sound English
- [ ] Figures/tables self-contained with units and **SED/LSD/CI** (see `fcr-figures-and-tables`)

### Reporting completeness
- [ ] Crop/cultivar, sites/seasons, soil, **weather vs. phenology**, management, design, statistics
- [ ] Yield data included/linked to biophysical process where relevant

### Declarations & files
- [ ] **Data-availability statement** drafted (shared + repository/ID, or restricted + reason)
- [ ] **Generative-AI** use declared; CRediT roles, funding, competing interests
- [ ] Cover letter establishing scope fit + contribution (see `fcr-cover-letter`)
- [ ] Co-submission to **Data in Brief / MethodsX** considered if relevant

## Anti-patterns

- Submitting controlled-environment-only or single-site/single-season work
- Abstract over length; highlights that are topics or exceed 85 characters
- Methods missing soil/weather-vs-phenology/management (not reproducible)
- Blank data-availability statement; missing generative-AI declaration
- A discussion that repeats results; means with no error term

## Output format

```
【Scope & type】field-based + ≥2 seasons/envs + field crop + general; type chosen? [Y/N]
【Abstract & highlights】≤~400 words; 3-5 bullets ≤85 chars? [Y/N]
【Reporting complete】cultivar/site/soil/weather-vs-phenology/management/design/stats? [Y/N]
【Declarations】data availability + generative-AI + CRediT/funding? [Y/N]
【Cover letter】scope fit + contribution stated? [Y/N]
【Next】await decision → fcr-revision-and-rebuttal on a revise verdict
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers and Elsevier typesetting/templates
- [`../../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 →