Agent skill · Code Review & Quality

agsy-workflow

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.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-workflow --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Agricultural-Systems-Skills/skills/agsy-workflow/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agricultural Systems Workflow Router (agsy-workflow) The orchestrator for an Agricultural Systems submission. Figure out the stage and the **article type**, then send the user to the matching skill. AgSy is defined by **interactions across components and hierarchical levels** (field → farm → landscape → region → food system) — the router's first job is to make sure the paper poses a genuine **systems** question, analyzed with **modelling and trade-offs**, not a single-factor agronomic trial. ## When to trigger - Starting a new AgSy 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 `agsy-revision-and-rebuttal`) ## First question: is this a systems paper, and which type? | Situation | Article type | Route to | |-----------|--------------|----------| | Full systems study (interactions, modelling, trade-offs) | **Research paper** (~8,000 words) | normal pipeline below | | One focused systems result | **Short communication** (~4,000 words) | normal pipeline, tighter scope | | Forward-looking opinion on agricultural-systems science | **Perspective** (~2,000 words

What's inside
Steps it walks through
  1. When to trigger
  2. First question: is this a systems paper, and which type?
  3. Routing map (stage → skill)
  4. Default order
  5. Worked routing example (illustrative)
  6. Anti-patterns
  7. Router pass for Agricultural Systems
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the agsy-workflow skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going