jru-submission
Use when running the final pre-submission preflight for the Journal of Risk and Uncertainty (JRU) via Springer's portal — file set, anonymization, Data Availability Statement, ethics and AI disclosures, and house-style checks. Final checks; it does not draft content.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-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 (jru-submission) ## When to trigger - "Submitting this week" — last pass before uploading to Springer's submission system - Unsure which files Springer's Editorial Manager expects, or how to anonymize for review - Confirming the Data Availability Statement, ethics, funding, and AI-use disclosures are in place - Verifying the abstract, length, and reference style conform befo
What does the jru-submission skill do?
Use when running the final pre-submission preflight for the Journal of Risk and Uncertainty (JRU) via Springer's portal — file set, anonymization, Data Availability Statement, ethics and AI disclosures, and house-style checks. Final checks; it does not draft content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-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.