Agent skill · Code Review & Quality

agsy-literature-positioning

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.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-literature-positioning --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-literature-positioning/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

# Literature Positioning (agsy-literature-positioning) AgSy is read by a **systems-science** audience that spans crop and livestock modelling, whole-farm and bio-economic analysis, sustainability assessment, and food-system science. Positioning is therefore not throat-clearing — the paper must show it advances the **systems and modelling** conversation, not just add another data point to one subfield. ## When to trigger - Drafting or revising the introduction and the "contribution" paragraph - A reviewer said you "ignored the relevant modelling work" or "don't engage the systems debate" - Your agronomic or model results are solid but the framing reads as single-discipline - You need to distinguish your contribution from the closest prior systems studies / models ## How AgSy wants the literature engaged 1. **Engage the systems debate, not a citation pile.** Identify the open systems question — an unresolved trade-off, a contested mechanism, a model limitation, a scaling gap — that your paper addresses. Cite the works that *define* it. 2. **Two literatures at once.** The **domain** literature (the crop/livestock/farm/food system you study) **and** the **methods** literature (the mode

What's inside
Steps it walks through
  1. When to trigger
  2. How AgSy wants the literature engaged
  3. Cross-system engagement (a distinctive AgSy demand)
  4. Worked micro-example: locating one contribution (illustrative)
  5. Referee pushback → the AgSy-specific fix
  6. Anti-patterns
  7. Positioning pass for Agricultural Systems
  8. Output format
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the agsy-literature-positioning skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-literature-positioning --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