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 the Journal of Risk and Uncertainty (JRU) via Springer's portal — file set, anonymization, Data Availability Statement…
MITAuto-check passed
Install Jru Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission .claude/skills/jru-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 "jru-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission into .claude/skills/jru-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-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 jru-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission .agents/skills/jru-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 "jru-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission into .agents/skills/jru-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-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 jru-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission .cursor/skills/jru-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 "jru-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission into .cursor/skills/jru-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-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 Journal-of-Risk-and-Uncertainty-Skills/skills/jru-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 jru-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission .gemini/skills/jru-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 "jru-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission into .gemini/skills/jru-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-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 jru-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 jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission .github/skills/jru-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 "jru-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission into .github/skills/jru-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-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 jru-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 jru-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/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission .opencode/skills/jru-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 "jru-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission into .opencode/skills/jru-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jru-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
jru-submission- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 715 words
- Files
- 3
- 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 the Journal of Risk and Uncertainty (JRU) via Springer's portal — file set, anonymization, Data Availability Statement…
- Running the final pre-submission preflight for the Journal of Risk and Uncertainty (JRU) via Springers portal — file set
- SKILL.md covers When to trigger, Process facts (检索于…, Preflight checklist and Cover letter for a specialist…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Data Availability Statement
What it does
Jru Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `templates/checklist.md` and `templates/manuscript_template.md`).
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
- Running the final pre-submission preflight for the Journal of Risk and Uncertainty (JRU) via Springers portal — file set
- Data Availability Statement
- Ethics and AI disclosures
- House-style checks
Example prompts
- “/jru-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
Jru Submission loads about 1.6k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 715 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). 715 words, ~1,575 tokens.
Download SKILL.mdSave it as
.claude/skills/jru-submission/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- jru-submission
- description
- 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.
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 before the editor sees the paper
Process facts (检索于 2026-06；以官网为准)
- JRU is published by Springer (Springer Science+Business Media); content sits on Springer Nature Link (ISSN 0895-5646 print / 1573-0476 electronic). Editor-in-Chief and founder: W. Kip Viscusi (Vanderbilt), who has led the journal since 1988 (re-verified 2026-06-22 against the Springer editorial-board page; re-confirm before relying).
- Submission is through Springer's online system (Editorial Manager, the Springer standard — 待核实 against the live guidelines); the Editor-in-Chief reserves the right to reject submissions that do not meet the author guidelines.
- Review model: single-blind is the Springer econ default — 待核实; confirm whether JRU anonymizes. If single-blind, author identities are visible to referees and need not be stripped, but verify before relying on it.
- Data Availability Statement is required on original research articles; Springer strongly encourages depositing underlying data in a recognized repository.
- Exact abstract word limit, manuscript length cap, and any open-access / APC fees are 待核实 — read them off the official submission guidelines at submission time.
- ORCID is recommended for submitting authors.
Preflight checklist
Manuscript & style
- Abstract within the journal's word limit (待核实 — verify cap); keywords and JEL codes included
- Title page with full affiliations; corresponding author and ORCID set
- References in the journal's style (Springer basic / numbered — 待核实); every in-text cite resolves
- Figures plot the key functions (w(p), value function) with the EU benchmark; tables report SE/CI, not bare asterisks
- Experiment instructions / decision screens included as supplementary material; estimand stated in the main text
Files & disclosures for the Springer portal
- Main manuscript + supplementary appendix; experiment materials and code as supplementary files or repository link
- Data Availability Statement present and consistent with what is deposited
- Ethics / IRB approval stated for human-subjects experiments; consent noted
- Competing-interests and funding declarations complete
- AI/LLM use disclosed per Springer policy; AI not listed as an author
- Anonymization handled per the confirmed review model (待核实)
Sibling-fit last look
- The paper's object is a risk/uncertainty primitive — not a method demo (Experimental Economics) or a broad-behavioral result (JEBO); the cover letter says why JRU
Final consistency sweep
- Every number in the abstract matches the corresponding table to the last digit
- Notation in the text matches the notation in the figures and table notes
- All in-text citations appear in the reference list and vice versa
- Supplementary files referenced in the text are actually uploaded
- Author list, affiliations, and ORCIDs are final (changes after submission are friction)
- The paper does not assert a fact about the journal (limit, fee, policy) that is not verified — anything uncertain is left out, not guessed
Show full SKILL.md (250 more words)Show less
Cover letter for a specialist desk
The Editor-in-Chief screens for fit, so the cover letter does real work at JRU:
- One sentence on the primitive. Name the risk/uncertainty object the paper moves (a representation, an elicited parameter, a VSL, an insurance elasticity).
- One sentence on why JRU, not a sibling. Pre-empt the desk question: this is a risk/uncertainty contribution, not a method demo (Experimental Economics) or a broad behavioral result (JEBO).
- Suggested and excluded reviewers if the system allows — useful in a small specialized pool where conflicts and rival camps are real.
- Prior-submission note if the paper was previously reviewed elsewhere and substantially revised.
What to expect after submission
- Single-blind specialist review (待核实) typically yields a few deep technical objections rather than many shallow ones; budget revision time for new analyses, not just edits.
- The binding decision usually turns on the decision-theoretic or measurement core, so an R&R will most often ask you to shore up the representation or the identification (
jru-theory-model/jru-identification).
Anti-patterns
- Uploading without a Data Availability Statement (required even when data are restricted)
- Reporting significance with asterisks instead of standard errors / confidence intervals
- Omitting experiment instructions — for an elicitation paper the procedure is part of the method
- Assuming a word/abstract limit or a fee instead of reading the live guidelines (mark 待核实)
- A cover letter that does not say why the paper is JRU and not a sibling venue
Output format
【Manuscript】abstract within cap (待核实) + keywords + JEL? [Y/N]
【Exhibits】functions plotted vs. EU benchmark; SE/CI not stars? [Y/N]
【Data Availability Statement】present + consistent with deposit? [Y/N]
【Ethics/IRB + funding + AI disclosure】complete? [Y/N]
【Experiment materials】instructions/screens/code supplied? [Y/N]
【Fit】cover letter argues JRU over Experimental Economics / JEBO? [Y/N]
【Next step】submit via Springer portal → jru-rebuttal for what to expectSupplementary resources
templates/checklist.md— submission self-checktemplates/manuscript_template.md— lightweight manuscript scaffold../../resources/official-source-map.md— official Springer URLs and volatile facts
© 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
SKILL.md and 2 other files in Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission of brycewang-stanford/Awesome-Journal-Skills.
- SKILL.md
- templates/checklist.md
- templates/manuscript_template.md
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jru 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 |
|---|---|---|---|---|---|---|
| Jru Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 Jru Submission
What does Jru Submission do?
A skill your agent uses 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…. Jru Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Jru Submission?
Jru Submission fits situations like: running the final pre-submission preflight for the Journal of Risk and Uncertainty (JRU) via Springers portal — file set; data Availability Statement; ethics and AI disclosures; house-style checks.
How do I install Jru Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-submission -a claude-code`. Or copy the skill folder (Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jru-submission in your project. Claude Code loads it when a task matches its description.
How do I install Jru Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-submission -a codex`. Or copy the skill folder (Journal-of-Risk-and-Uncertainty-Skills/skills/jru-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jru-submission in your project. Codex loads it when a task matches its description.
Can I use Jru 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 jru-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/jru-submission, .gemini/skills/jru-submission, .github/skills/jru-submission and .opencode/skills/jru-submission in your project.
What does Jru Submission need to run?
SKILL.md names no scripts, command-line tools or credentials: Jru Submission is instructions for the agent only.
Does Jru 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 Jru 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 Jru Submission use?
Jru 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 Jru Submission use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Jru Submission?
Skills that share tags, products or a category with Jru 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 Jru 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.