Use when drafting or polishing an Agricultural Systems (AgSy) manuscript so it reads clearly for a systems-science audience, follows the journal's format, and meets front-matter requirements (abstract <= 250 words, Highlights, graphical abstract). Research papers run to about 8,000 words (no hard cap). Tightens prose and format; it does not invent content.
NewMaintained
Automatic
◆Writing & Editing pack
Last verified 8/15/2026
What it changes
Passed 18 of 25 test cases with the skill, and 18 of 25 without it.
Without skill72%
With skill72%
0 fixed18 passed either way7 still failing0 broke
Pass-rate lift
0 pp
Tokens
+31%
Agent turns
0%
Response time
-30%
Model gemini-3.6-flashMeasured 8/15/2026v118 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md101 linessingle file
Writing Style (agsy-writing-style)
An AgSy paper must be readable by a broad systems-science audience — agronomists, modellers,
economists, and environmental scientists — and prepared with the journal's front matter. This skill is
about communicating a systems analysis clearly and meeting Elsevier's format, not about generating
claims.
When to trigger
Drafting the introduction, framing the contribution, or final polish
Writing the ≤ 250-word abstract, the Highlights, or the graphical abstract
Tightening a long methods/results section toward the ~8,000-word guideline
Aligning references and format to the journal's style before submission
Reach the systems-science audience
Front-load the systems contribution. By the end of the introduction the reader knows the system,
the interaction/trade-off in question, the modelling approach, and why the result matters. Don't make
a reader dig for the "so what."
Define the system early. State boundary, components, and hierarchical level so a non-specialist
in your exact subsystem can follow (see agsy-systems-framing-and-modeling).
Explain the model in plain terms first, then in detail. A reader should grasp what the model does
before meeting its equations.
Argument-first prose. Lead with the systems insight; use model output and statistics to support
it. Avoid "the model shows…" without saying what it shows about the system and why it matters.
Signpost. Clear IMRaD-style structure so a reader can navigate framing → model → evaluation →
trade-offs → implications.
Format & front matter (source map refreshed 2026-06-20)
Abstract: ≤ 250 words, stating purpose, principal results, and major conclusions.
Highlights: 3-5 short bullet points, each no more than 85 characters including spaces.
Graphical abstract: a separate figure file summarizing the work for an interdisciplinary audience
— often a conceptual system diagram or a trade-off result; live-check current size/format specs.
References: format to the journal's style; manage with Zotero/Mendeley/BibTeX (Elsevier
elsarticle for LaTeX).
Declarations: CRediT roles, declaration of competing interest, funding, and AI-use disclosure
where applicable (see agsy-submission).
Length discipline (research paper ~8,000 words; no hard cap)