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 Workflow

ASecurity

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.

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

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-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agsy Workflow?

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

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

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

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

# 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, rapid review) | `agsy-writing-style` + `agsy-impact-and-implications` |
| Short response to a published AgSy paper | **Comment** (~1,000 words) | `agsy-literature-positioning` + `agsy-writing-style` |
| Integrative synthesis of a systems literature | **Review** (verify scope) | `agsy-literature-positioning` + `agsy-systems-framing-and-modeling` |

> If the work is really a single-treatment field trial with no interactions, trade-offs, or model, it
> is **off-fit** — reframe it as a systems question or send it to a field-crops/agronomy journal.

## Routing map (stage → skill)

```text
Is it a real systems question?     → agsy-topic-selection
Where does it sit in the field?    → agsy-literature-positioning
System boundaries + the model?     → agsy-systems-framing-and-modeling
Is the model evaluated soundly?    → agsy-data-and-model-evaluation
Do exhibits show interactions?     → agsy-figures-and-tables
Does it read clearly?              → agsy-writing-style
Why does the result matter?        → agsy-impact-and-implications
Data + code + models shareable?    → agsy-reproducibility-and-data-policy
How will it be judged?             → agsy-review-process
Ready to submit?                   → agsy-submission
Got reviews / a decision?          → agsy-revision-and-rebuttal
```

## Default order

`topic-selection → literature-positioning → systems-framing-and-modeling → data-and-model-evaluation →
figures-and-tables → writing-style → impact-and-implications → reproducibility-and-data-policy →
review-process → submission → revision-and-rebuttal`

Iterate: most systems papers loop framing ↔ modelling ↔ evaluation several times before writing-style.

## Anti-patterns

- Treating AgSy like a field-trial agronomy journal — the contribution must be a systems analysis
- A model run with no description, calibration, or evaluation (a black box)
- Skipping the decision/impact step — AgSy wants relevance, not a methods demo
- Leaving data, code, and the model undocumented until acceptance

## Output format

```
【Stage】idea / positioning / framing / evaluation / exhibits / writing / impact / repro / review / submit / revise
【Article type】Research paper / Short communication / Perspective / Comment / Review
【Systems question?】real interactions/trade-offs? [Y/N]
【Route to】agsy-<skill>
【Why】one line
【Then】the next skill after that
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — systems models + calibration/uncertainty software by scale
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — official AgSy URLs behind every fact in this pack

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 →