Running CI Preflight
PostHog/posthog
Catch the deterministic CI failures reachable from your diff before pushing, with hogli ci:preflight.
A skill your agent uses when running the final pre-submission preflight for Agricultural Systems (AgSy) via the current Elsevier submission path / Editorial Manager — article-type selection…
MITAuto-check passed
Install Agsy Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills agsy-submission --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Agricultural-Systems-Skills/skills/agsy-submission .claude/skills/agsy-submission && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agsy-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submission into .claude/skills/agsy-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agsy-submission", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submissionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills agsy-submission --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Agricultural-Systems-Skills/skills/agsy-submission .agents/skills/agsy-submission && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agsy-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submission into .agents/skills/agsy-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agsy-submission", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills agsy-submission --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Agricultural-Systems-Skills/skills/agsy-submission .cursor/skills/agsy-submission && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agsy-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submission into .cursor/skills/agsy-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agsy-submission", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Agricultural-Systems-Skills/skills/agsy-submission--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills agsy-submission --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Agricultural-Systems-Skills/skills/agsy-submission .gemini/skills/agsy-submission && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agsy-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submission into .gemini/skills/agsy-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agsy-submission", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills agsy-submissionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Agricultural-Systems-Skills/skills/agsy-submission .github/skills/agsy-submission && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agsy-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submission into .github/skills/agsy-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agsy-submission", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills agsy-submission --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Agricultural-Systems-Skills/skills/agsy-submission .opencode/skills/agsy-submission && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agsy-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Agricultural-Systems-Skills/skills/agsy-submission into .opencode/skills/agsy-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agsy-submission", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agsy-submission- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 698 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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
- SKILL.md covers When to trigger, Process facts (source map…, Preflight checklist and Anti-patterns, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Graphical abstract
What it does
Agsy Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Abstract <= 250 words
- Graphical abstract
- CRediT and declaration-of-interest statements
- Funding/AI disclosures
Example prompts
- “/agsy-submission”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agsy Submission loads about 1.7k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 698 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 698 words, ~1,724 tokens.
Download SKILL.mdSave it as
.claude/skills/agsy-submission/SKILL.md (or your agent's skills folder).- name
- agsy-submission
- description
- 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.
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, Perspective, and book-review submissions should be discussed with editors first where the Guide requires it.
- Abstract: ≤ 250 words.
- Highlights: required at submission; 3-5 bullets, each max 85 characters including spaces.
- Graphical abstract: required as a separate file; check the current pixel/format specs before upload.
- Declarations: CRediT author-contribution statement; declaration of competing interest; funding sources; generative-AI disclosure when AI tools were used.
- Data/code/model: Option C repository deposit + dataset citation/link + data-availability statement, or a reason sharing is not possible.
- Fee: Open Access APC USD 3,850 excluding taxes; subscription route has no publication fee charged to authors (verified 2026-06-22; re-check the live ScienceDirect figure before submission).
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 (3-5 bullets, max 85 characters each); 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
- Funding and AI-use disclosures complete; 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 funding or AI-use disclosure where required
- 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)
Show full SKILL.md (266 more words)Show less
Worked micro-example (illustrative)
A crop–livestock simulation study with scenario analysis is readied for upload; the preflight catches three avoidable failures:
- Abstract = 268 words → over the 250 cap. Trimmed to 242 by cutting two methods sentences and one caveat, keeping purpose, principal result, and the trade-off conclusion.
- No graphical abstract → a conceptual crop–livestock system diagram is prepared, satisfying the requirement and doubling as the framing exhibit.
- Model deposited, run scripts not → Elsevier counts code and models as research data, so run
scripts and parameter files are added to the deposit and the data-availability statement links the
DOI, pre-empting a late reproducibility hold (see
agsy-review-process).
Result: a clean upload rather than three Editorial Manager bounce-backs.
Desk-reject patterns this preflight catches
- Fit failure. A single-factor field trial with no interactions, model, or trade-off reads as an
agronomy paper at a systems journal — reframe via
agsy-topic-selectionor re-route. - Black-box model. No version, calibration, evaluation, or deposit → the model cannot be assessed.
- Wrong track. A full study compressed into Perspective length, or a Perspective padded into a research paper — type/length mismatch is an early screen.
- Incomplete front matter. Missing Highlights, graphical abstract, CRediT, COI, funding, or AI-use disclosure stalls the submission before review starts.
Calibration anchors
- The ≤250-word abstract, 3-5 Highlights, graphical abstract, CRediT roles, competing-interest declaration, funding disclosure, AI-use disclosure, and Option C data statement are the current pre-submission checks.
- Re-open the ScienceDirect Submit your article link and Guide for Authors before upload because URLs, fees, and file specs can change.
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 + funding/AI disclosure? [Y/N]
【Data/code/model】deposited + availability statement? [Y/N]
【References】journal style consistent? [Y/N]
【Next】await decision → agsy-revision-and-rebuttal on revisionSupplementary resources
../../resources/external_tools.md— reference managers, typesetting, repositories../../resources/official-source-map.md— official AgSy URLs behind every fact in this pack
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Agricultural-Systems-Skills/skills/agsy-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Agsy Submission next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agsy Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Running CI PreflightPostHog/posthog | 40k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Finalize Agent Promptgithub/awesome-copilot | 40k | 1 repos | ~224 | Automated safety check: Pass | MIT | |
| Azure Deployment Preflightgithub/awesome-copilot | 40k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Implementation Final Reviewopenai/openai-agents-python | 30k | — | ~2k | Automated safety check: Pass | MIT | |
| Preflightopenwpm/OpenWPM | 1.4k | — | ~670 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
- Official
Finalize Agent Prompt
github/awesome-copilot
Finalize prompt file using the role of an AI agent to polish the prompt for the end user.
- Official
Azure Deployment Preflight
github/awesome-copilot
Performs comprehensive preflight validation of Bicep deployments to Azure, including template syntax validation, what-if analysis, and permission checks.
- Official
Implementation Final Review
openai/openai-agents-python
Review completed implementation changes before final verification.
Preflight
openwpm/OpenWPM
Use BEFORE implementing code in a crosslink-tracked project — loads .crosslink/rules/global.md, the language rules for detected manifests, the project rules, and the active tracking-<mode.md.
Preflight
openfootmanager/openfootmanager
Verify a pull request with the frontend scripts, default and MCP backend tests and clippy, formatting, architecture checks and review evidence.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Agsy Submission
What does Agsy Submission do?
A skill your agent uses when running the final pre-submission preflight for Agricultural Systems (AgSy) via the current Elsevier submission path / Editorial Manager — article-type selection…. Agsy Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Agsy Submission?
Agsy Submission fits situations like: abstract <= 250 words; graphical abstract; CRediT and declaration-of-interest statements; funding/AI disclosures.
How do I install Agsy Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a claude-code`. Or copy the skill folder (Agricultural-Systems-Skills/skills/agsy-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/agsy-submission in your project. Claude Code loads it when a task matches its description.
How do I install Agsy Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a codex`. Or copy the skill folder (Agricultural-Systems-Skills/skills/agsy-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/agsy-submission in your project. Codex loads it when a task matches its description.
Can I use Agsy Submission in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill agsy-submission -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agsy-submission, .gemini/skills/agsy-submission, .github/skills/agsy-submission and .opencode/skills/agsy-submission in your project.
What does Agsy Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Agsy Submission is instructions for the agent only.
Does Agsy Submission access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Agsy Submission safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Agsy Submission use?
Agsy Submission is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agsy Submission use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Agsy Submission?
Skills that share tags, products or a category with Agsy Submission: Running CI Preflight (PostHog/posthog, 40k stars), Finalize Agent Prompt (github/awesome-copilot, 40k stars), Azure Deployment Preflight (github/awesome-copilot, 40k stars) and Implementation Final Review (openai/openai-agents-python, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agsy Submission?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.