Agent skill · Data & Analytics

jru-replication-package

Use when assembling the data, code, and experiment materials for a Journal of Risk and Uncertainty (JRU) manuscript and writing its Data Availability Statement. Builds a transparent, reproducible package; it does not invent evidence or citations.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-replication-package --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: Journal-of-Risk-and-Uncertainty-Skills/skills/jru-replication-package/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Replication Package (jru-replication-package) ## When to trigger - The paper has experimental or field results and you need a Data Availability Statement for the Springer submission - z-Tree / oTree / Qualtrics materials and the structural estimation code exist but are not organized for a stranger to run - A referee or the editor asks whether the elicitation could be reproduced from the materials provided - Decisions about what data can be shared (human-subjects constraints) versus what must be documented are unsettled ## What JRU / Springer expect JRU requires a **Data Availability Statement** on original research articles, and Springer strongly encourages sharing the underlying research data (deposit in a recognized repository, with a citable DOI where possible). For this journal the package has two faces that generic econ replication advice misses: the **experiment must be reproducible as a procedure** (instructions, screens, incentive rules — not just the resulting dataset), and the **structural estimation must be re-runnable** (code that recovers the reported parameters). Exact policy wording and any mandatory-deposit details are 待核实 — verify on the official submission guide

What's inside
Steps it walks through
  1. When to trigger
  2. What JRU / Springer expect
  3. The two-face package
  4. Human-subjects and proprietary data
  5. Layout that a stranger can run
  6. Writing the Data Availability Statement
  7. Checklist
  8. Common reproducibility failures in risk papers
  9. Anti-patterns
  10. Worked vignette (illustrative)
  11. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jru-replication-package skill do?

Use when assembling the data, code, and experiment materials for a Journal of Risk and Uncertainty (JRU) manuscript and writing its Data Availability Statement. Builds a transparent, reproducible package; it does not invent evidence or citations.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-replication-package --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.

Keep going