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 Writing Style

ASecurity

Use when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format expectations (abstract ~400 words, 3-5 highlights of <=85 characters, grammatically sound English, concise results, a discussion that interprets rather than repeats). Tightens prose and format; it does not invent 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-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fcr Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: fcr-writing-style
description: Use when drafting or polishing a Field Crops Research (FCR) manuscript so it reads for a general agronomy/crop-science audience, follows FCR structure, and meets the format expectations (abstract ~400 words, 3-5 highlights of <=85 characters, grammatically sound English, concise results, a discussion that interprets rather than repeats). Tightens prose and format; it does not invent content.
---

# Writing Style (fcr-writing-style)

An FCR paper must be readable by an agronomist or crop scientist outside your exact crop and region,
written in **grammatically sound English**, and disciplined to FCR's structure: a focused
introduction, complete methods, **concise results that address the objectives**, and a **discussion
that interprets rather than restates** results. This skill is about clarity and format — not about
generating claims.

## When to trigger

- Drafting the introduction, results, or discussion, or doing a final polish
- Writing the **abstract** (≈ 400 words) and the **highlights** (3–5 bullets)
- Tightening a verbose results or discussion section
- Aligning citations and units to the Elsevier/FCR style before submission

## Structure & section discipline

1. **Introduction.** Brief, unbiased, up-to-date review that flows to clear **objectives or
   hypotheses** of general relevance (see `fcr-literature-positioning`).
2. **Materials & Methods.** Complete enough to reproduce: crop/cultivar, sites/seasons, soil, weather,
   management, design, and statistics (see `fcr-reporting-and-data-policy`).
3. **Results.** **Concise**; report what answers the objectives, with effect sizes and uncertainty.
   Do not interpret here.
4. **Discussion.** **Place findings in agronomic context** and justify conclusions with the data — do
   **not** repeat the results. State scope/limitations and generality across environments.

## Abstract & highlights

- **Abstract** (**≤ ~400 words**, 待核实 exact cap): purpose, key methods (crop, environments),
  principal quantitative results, and the major agronomic conclusion.
- **Highlights**: **3–5 bullet points, each ≤ 85 characters including spaces** — concrete findings,
  not topic labels.

## Reach a general agronomy audience

- Define crop- or region-specific terms on first use; spell out acronyms; use **SI units** throughout.
- Lead with the agronomic point; connect results to **yield and biophysical processes**.
- Quantify ("a 0.8 t ha⁻¹ increase," not "a large increase"); avoid vague significance language.
- Signpost clearly so a reader can follow the argument from objective to conclusion.

## Anti-patterns

- A discussion that repeats the results instead of interpreting them
- A region-insider framing that never states general relevance
- An abstract that hides the quantitative finding or runs far over length
- Highlights that are topics ("Effects of nitrogen on wheat") rather than findings
- Non-SI units, undefined acronyms, or inconsistent citation style
- Conclusions not justified by the data

## Output format

```
【Structure】intro → methods → concise results → interpretive discussion? [Y/N]
【Discussion interprets, not repeats?】[Y/N]
【Abstract】word count (≈≤400) + states quantitative finding? [Y/N]
【Highlights】3-5 bullets, each ≤85 chars, findings not topics? [Y/N]
【General reach】SI units + acronyms defined + quantified? [Y/N]
【Next】fcr-cover-letter
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers and Elsevier typesetting tools
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — abstract/highlights specs and structure expectations

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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', ...

686011 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.

651 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 →