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

Agsy Topic Selection

ASecurity

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.

1,052 stars
0 votes
0 copies
1 views
Added 6/4/2026
ai-agentsapisecurity

Works with

api

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-topic-selection --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agsy Topic Selection?

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

Security grade badge for Agsy Topic Selection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-agsy-topic-selection/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-agsy-topic-selection)

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

Download with Pro
Files
SKILL.md
---
name: agsy-topic-selection
description: 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.
---

# Topic Selection & Fit (agsy-topic-selection)

Agricultural Systems publishes the **systems analysis of agricultural systems**. The bar is not "a new
result for crop X" — it is **"a systems question about interactions and trade-offs."** Use this skill to
pressure-test fit before you invest, and to keep a field trial from being mistaken for a systems paper.

## When to trigger

- Choosing among possible projects or framings for an AgSy submission
- A reviewer/colleague said the paper "is just a field trial" or "lacks a systems angle"
- Deciding between a **research paper** and a **short communication**
- Considering a **perspective** (forward-looking opinion) or a **comment** on a published paper

## The AgSy fit test

A strong AgSy paper usually clears all four:

1. **A real systems question.** The object is **interactions** — among components (crop–soil–livestock–
   economics), across hierarchical levels, between agriculture and other land uses, or with the
   natural/social/economic environment. If nothing interacts, it is not a systems paper.
2. **Whole-farm to food-system scope (preferred).** AgSy gives preference to **whole-farm and
   landscape-level** issues. A plot-level result needs to be scaled or embedded in a larger system.
3. **Integrated modelling and trade-offs.** Conceptual + empirical + **dynamic / bio-economic
   modelling**; the analysis surfaces **trade-offs and synergies**, not a single optimal number.
4. **Decision relevance.** The result informs a design, management, or policy choice (see
   `agsy-impact-and-implications`).

## Scale & system-boundary framing (state your system explicitly)

| If your work is at… | reach AgSy fit by… |
|---------------------|---------------------|
| Field / plot | scaling to the farm or showing the field-level interaction that matters to the system |
| Whole-farm | the journal's sweet spot — show component interactions and whole-farm trade-offs |
| Landscape / region | spatial interactions, land-use competition, aggregation/emergence across farms |
| Food system | linking production to value chains, food security, environment, and policy |

## Article-type choice

- **Research paper** — full systems study, **~8,000 words** (no hard cap; stay near it).
- **Short communication** — one crisp systems result, **~4,000 words**. Do not pad it into a paper.
- **Perspective** — a forward-looking argument about agricultural-systems science, **~2,000 words**,
  **rapid review** (see `agsy-review-process`).
- **Comment** — a focused response to a published AgSy paper, **~1,000 words**.

## Anti-patterns

- A single-factor field trial with no interactions, model, or trade-off (off-fit — send to an agronomy journal)
- "First time simulated in country X" as the whole contribution (descriptive, not a systems advance)
- A model demo with no agricultural-systems question or decision payoff
- Choosing research-paper length out of habit when a short communication would land harder

## Output format

```
【Question】one sentence (state the interaction / trade-off)
【System & boundary】components + hierarchical level(s) + scale
【Modelling approach】conceptual / empirical / dynamic / bio-economic
【Decision relevance】who acts differently if this is true
【Article type】Research paper / Short communication / Perspective / Comment / Review
【Fit verdict】strong / needs reframing / off-fit (why)
【Next】agsy-literature-positioning
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — systems models and data sources by scale
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — AgSy aims, scope, and article types

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

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

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

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