Agricultural Systems Skills

Use as the entry point for any Agricultural Systems (AgSy) manuscript. Routes to the right AgSy sub-skill based on where you are in the lifecycle and which article type (research paper, short communication, perspective, comment, review) fits. AgSy is a systems-science journal, so the router's first job is to confirm there is a real systems question — interactions, hierarchical levels, trade-offs — not a single-factor field trial. It dispatches; it does not draft content.

Use when running the final pre-submission preflight for Agricultural Systems (AgSy) via the current Elsevier submission path / Editorial Manager — article-type selection, abstract <= 250 words, Highlights, graphical abstract, CRediT and declaration-of-interest statements, funding/AI disclosures, reference style, and data/code/model availability. Final checks; it does not draft content.

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.

Use to understand how Agricultural Systems (AgSy) evaluates a manuscript — single-anonymized peer review with a minimum of two reviewers and an editor decision, desk screening for fit and systems content, what reviewers weigh, and the rapid-review track for Perspectives. Sets expectations and shapes the paper to survive review; it does not contact editors.

Use when deciding whether a project fits Agricultural Systems (AgSy) and which article type to target. AgSy is a systems-science journal, so the test is a genuine systems question — interactions among components, across hierarchical levels (field → farm → landscape → region → food system), trade-offs, and emergent behavior — analyzed with integrated modelling, NOT a single-factor field trial. Helps frame the question; it does not collect data.

Use when building figures and tables for an Agricultural Systems (AgSy) manuscript so exhibits communicate interactions, dynamics, trade-offs, and model performance clearly. AgSy is a systems journal, so the best exhibits show trade-off frontiers, observed-vs-simulated fit, resource flows, and conceptual system diagrams — not just a bar chart of one treatment. Designs exhibits; it does not run the analysis.

Use when writing the response to an Agricultural Systems (AgSy) revision decision. AgSy review is single anonymized with at least two expert systems reviewers and an editor decision, and revisions often turn on model evaluation, sensitivity/uncertainty, and trade-off framing. The response must convert each reviewer without alienating the editor. Structures the response letter; it does not fabricate new results.

Use when positioning an Agricultural Systems (AgSy) manuscript against the literature so it reads as a systems contribution. AgSy readers span agronomy, modelling, livestock, economics, environment, and food-system science, so the paper must engage the systems and modelling literatures they expect — not only one subfield. Stakes the contribution; it does not write the lit review.

Use when articulating why an Agricultural Systems (AgSy) result matters — its relevance for farm design, management, decision support, or policy. AgSy values systems analysis that informs a decision, so this is what separates an AgSy paper from a methods demo. It frames implications honestly within the model's scope; it does not over-claim or invent impact.

Use when evaluating the model and analyzing results for an Agricultural Systems (AgSy) manuscript so it survives expert systems review — independent model evaluation (observed vs. simulated, fit statistics), sensitivity and uncertainty analysis, and trade-off / scenario analysis across the system. Guides evaluation norms; it does not fabricate results or run the model.

Use when framing the system and describing the model for an Agricultural Systems (AgSy) manuscript — defining system boundaries, components, hierarchical levels, and feedbacks, then choosing, describing, and calibrating the model (process/simulation, whole-farm, bio-economic, agent-based, or integrated assessment). This is the distinctive core of an AgSy paper. Structures the model and system; it does not run code for you.

Use when preparing the data, code, and model materials for an Agricultural Systems (AgSy) manuscript. AgSy applies Elsevier's research-data policy, which treats software, code, and models as research data — deposit them in a repository and cite/link them, or state why they cannot be shared. Covers model-description standards and exemptions. Prepares the materials; it does not waive requirements.