jhe-replication-package
Use when assembling the data, code, and access documentation for a Journal of Health Economics (JHE) manuscript — where much health data is restricted (claims, administrative, EHR) and the journal's policy encourages rather than mandates deposit. Packages reproducibility and a credible restricted-data access path; it does not run the analysis.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhe-replication-package --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.
# Replication Package (jhe-replication-package) ## When to trigger - The analysis uses restricted health data (Medicare/Medicaid claims, hospital discharge, EHR, registry, survey-linked admin) and you must document an access path - A Data Availability Statement and code package need assembling for submission - A referee or editor asks whether the results are reproducible despite data being non-public - You are deciding what can be deposited publicly versus what stays behind a Data Use Agreement / IRB ## What JHE actually requires (and what it does not) JHE follows the Elsevier **Research Data** policy: authors are **encouraged** to deposit data in a repository and to **state data availability at submission** — this is *not* the AEA's mandatory pre-publication openICPSR build-and-verify gate (检索于 2026-06；以官网为准). That softer baseline is precisely why credibility here rests on **how well you document the path to reproduction**, not on a public dataset that often cannot exist. The health-economics reality is that most rich data is restricted by privacy law (HIPAA), Data Use Agreements, and IRB. The professional standard JHE referees increasingly expect: **code is shareable even when da
- When to trigger
- What JHE actually requires (and what it does not)
- Build the package around the data's access tier
- Documentation that earns trust
- Checklist
- Why this matters more at JHE than at the AEA journals
- Anti-patterns
- Common restricted health-data sources and their access reality
- Worked vignette (illustrative)
- Output format
- Handoff boundary
What does the jhe-replication-package skill do?
Use when assembling the data, code, and access documentation for a Journal of Health Economics (JHE) manuscript — where much health data is restricted (claims, administrative, EHR) and the journal's policy encourages rather than mandates deposit. Packages reproducibility and a credible restricted-data access path; it does not run the analysis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhe-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.