jhr-replication-and-data-policy
Use when preparing Journal of Human Resources data and replication materials: archive plan footnote, public repository deposit, CC0 license, Data Availability Statement, read-me file, waiver requests, RCT pre-analysis-plan statements, and code package.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhr-replication-and-data-policy --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 & Data Policy (jhr-replication-and-data-policy) ## When to trigger - The paper is being prepared for JHR submission or acceptance - You need the archive-plan footnote, Data Availability Statement, or waiver - Data are restricted, proprietary, administrative, or RCT-based ## JHR policy core JHR's data policy is unusually concrete: accepted papers must preserve data and post replication materials in a well-curated public repository where possible, with a public-domain CC0 1.0 Universal license. At submission, include an archive plan footnote with a persistent link if available, or request a waiver at initial submission. ## Package contents - Data files that can legally be shared - Code and models needed to reproduce all tables and figures - Read-me file explaining the sequence - Data Availability Statement on the title page - Restricted-data access instructions or waiver justification - For RCTs: pre-analysis plan registration and deviations ## Acceptance-stage replication gate Do not wait until conditional acceptance to discover that the archive cannot be built. Run this gate before initial submission and again when the paper enters revision. | Gate | Pass condition |
- When to trigger
- JHR policy core
- Package contents
- Acceptance-stage replication gate
- Waiver logic
- Waiver evidence test
- Restricted-data package
- Deposit decisions by data source
- Exhibit-to-script map
- Worked waiver scenario: UI wage records
- Read-me skeleton for the JHR archive
- Pre-acceptance dry run
- Output format
What does the jhr-replication-and-data-policy skill do?
Use when preparing Journal of Human Resources data and replication materials: archive plan footnote, public repository deposit, CC0 license, Data Availability Statement, read-me file, waiver requests, RCT pre-analysis-plan statements, and code package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhr-replication-and-data-policy --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.