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 Submission

ASecurity

Use when running the final pre-submission preflight for Agricultural Systems (AgSy) via Editorial Manager — article-type selection, abstract <= 250 words, Highlights, graphical abstract, CRediT and declaration-of-interest statements, ORCID, reference style, and data/code/model availability. Final checks; 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-submission --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agsy Submission?

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

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

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

Download with Pro
Files
SKILL.md
---
name: agsy-submission
description: Use when running the final pre-submission preflight for Agricultural Systems (AgSy) via Editorial Manager — article-type selection, abstract <= 250 words, Highlights, graphical abstract, CRediT and declaration-of-interest statements, ORCID, reference style, and data/code/model availability. Final checks; it does not draft content.
---

# Submission Preflight (agsy-submission)

The last check before pressing submit on **Editorial Manager**. AgSy is **single anonymized**, so there
is no manuscript-anonymization step — but the front matter (abstract, Highlights, graphical abstract,
declarations) and the data/code/model availability statement are where avoidable failures happen.
Verify volatile specifics on the official page before relying on them.

## When to trigger

- "Submitting tomorrow" — last pass before upload
- Unsure which files/metadata Editorial Manager expects
- Confirming the article type's guideline length is met and all front matter is prepared

## Process facts (verify volatile items on the official page)

- **Publisher:** Elsevier (ISSN 0308-521X print / 1873-2267 online).
- **Portal:** **Editorial Manager** (legacy `ees.elsevier.com/agsy` redirects there — confirm current URL).
- **Review model:** **single anonymized** — no manuscript anonymization required (待核实).
- **Article types:** Research paper (~8,000 words), Short communication (~4,000), Perspective (~2,000,
  rapid review), Comment (~1,000), Review (verify) — no hard word cap, but stay near the guideline.
- **Abstract:** **≤ 250 words.**
- **Highlights** + **graphical abstract:** prepared.
- **Declarations:** **CRediT** author-contribution statement; **declaration of competing interest**;
  **ORCID** for authors.
- **Data/code/model:** repository deposit + data-availability statement (Elsevier research-data policy).
- **Fee:** subscription journal with a hybrid Gold OA option; confirm any APC after acceptance (待核实).

## Preflight checklist

### Article type & length
- [ ] Article type chosen; length near its guideline (research ~8,000 / short comm ~4,000 / perspective ~2,000 / comment ~1,000)
- [ ] Abstract ≤ 250 words; states purpose, principal results, major conclusions
- [ ] Highlights drafted; graphical abstract prepared

### Systems content (fit)
- [ ] The systems question (interactions / hierarchical levels / trade-offs) is explicit
- [ ] Model described, calibrated, and independently evaluated; sensitivity/uncertainty reported
- [ ] Decision / management / policy relevance stated (see `agsy-impact-and-implications`)

### Format & declarations
- [ ] References in the journal's style; consistent throughout
- [ ] **CRediT** roles + **declaration of competing interest** completed
- [ ] **ORCID** for authors; corresponding author and contact details correct
- [ ] Figures/tables self-contained and accessible (see `agsy-figures-and-tables`)

### Data, code & compliance
- [ ] Data + code + model deposited; **data-availability statement** in the manuscript
      (see `agsy-reproducibility-and-data-policy`)
- [ ] Ethics / funding / conflict declarations complete
- [ ] Original work; preprint status checked against Elsevier sharing policy

## Anti-patterns

- Abstract over 250 words; missing Highlights or graphical abstract
- No CRediT / competing-interest statement; missing ORCID
- A single-factor field trial sent to a systems journal (fit failure — see `agsy-review-process`)
- A black-box model with no calibration/evaluation or no data/code/model deposit
- Sending a full study to the Perspective track (wrong type and length)

## Output format

```
【Article type】Research / Short comm / Perspective / Comment / Review (length near guideline? Y/N)
【Abstract】word count (≤250); Highlights + graphical abstract? [Y/N]
【Systems content】question + model + evaluation + decision relevance? [Y/N]
【Declarations】CRediT + COI + ORCID? [Y/N]
【Data/code/model】deposited + availability statement? [Y/N]
【References】journal style consistent? [Y/N]
【Next】await decision → agsy-revision-and-rebuttal on revision
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers, typesetting, repositories
- [`../../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".

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