agsy-submission
Use when running the final pre-submission preflight for Agricultural Systems (AgSy) via the current Elsevier submission path / Editorial Manager — article-type selection, abstract <= 250 words, Highlights, graphical abstract, CRediT and declaration-of-interest statements, funding/AI disclosures, reference style, and data/code/model availability. Final checks; it does not draft content.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Submission Preflight (agsy-submission) The last check before pressing submit through the current Elsevier submission path / **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. Live-check 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 (source map refreshed 2026-06-20) - **Publisher:** Elsevier (ISSN 0308-521X print / 1873-2267 online). - **Portal:** current ScienceDirect **Submit your article** link / Editorial Manager path. - **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 — no hard word cap, but stay near the guideline. - **Consultation:** Review, Perspecti
- When to trigger
- Process facts (source map refreshed 2026-06-20)
- Preflight checklist
- Article type & length
- Systems content (fit)
- Format & declarations
- Data, code & compliance
- Anti-patterns
- Worked micro-example (illustrative)
- Desk-reject patterns this preflight catches
- Calibration anchors
- Output format
- Supplementary resources
What does the agsy-submission skill do?
Use when running the final pre-submission preflight for Agricultural Systems (AgSy) via the current Elsevier submission path / Editorial Manager — article-type selection, abstract <= 250 words, Highlights, graphical abstract, CRediT and declaration-of-interest statements, funding/AI disclosures, reference style, and data/code/model availability. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission --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.