From jhr-skills
Prepares Journal of Human Resources 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 this skill is triggered — by the user, by Claude, or both
Slash command
/jhr-skills:jhr-replication-and-data-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The paper is being prepared for JHR submission or acceptance
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.
Request a waiver at initial submission when data cannot be publicly deposited. State how other researchers can obtain the data and commit to provide reasonable guidance.
When the data cannot be public, still prepare:
| Data source | What can usually be deposited | Waiver posture |
|---|---|---|
| Public-use surveys (CPS, ACS, NLSY, PSID extracts) | Extraction code plus the analysis file, or code that rebuilds it from raw downloads | Rarely needed; check redistribution terms of each survey |
| State administrative records (UI wages, K-12, Medicaid) | Code, codebooks, aggregate exhibits; microdata stays with the agency | Waiver expected; document the access route precisely |
| Own RCT microdata | De-identified analysis files under CC0 where consent and IRB allow | Partial waiver for identifying fields; PAP registration stated |
| Proprietary/commercial data | Code, pseudo-data, purchase or license instructions | Waiver with a named acquisition path |
| Linked or matched files | Each source assessed separately; the crosswalk is often the binding constraint | Mixed: deposit what is public, waiver the link keys |
Repository choice and licensing details evolve — confirm against the journal's current author guidelines before depositing.
Illustrative case: earnings outcomes come from one state's unemployment-insurance wage records under a data-use agreement that bars any microdata release.
README
1. Data sources & access (public files included; restricted: how to apply)
2. Software & versions (Stata/R/Python; packages pinned)
3. Run order: 00_master -> 01_clean -> 02_analysis -> 03_exhibits
4. Runtime & hardware notes; random seeds fixed where used
5. Exhibit map: each table/figure -> producing script -> data requirement
6. License: CC0 1.0 Universal (data and code deposited)
[Data status] public / restricted / proprietary / confidential / mixed
[Archive plan footnote] ...
[DAS] ...
[Waiver needed] yes/no + reason
[RCT PAP status] ...
[Next step] jhr-submission
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jhr-skillsPrepares code and data archives required by the JFQA Code Sharing Policy for accepted post-2024 submissions. Builds source code, datasets, and read-me for deposit in the JFQA Dataverse.
Prepare data-availability statements and code/data archives for Journal of Corporate Finance submissions under Elsevier Research Data Option C.
Prepares research-data materials for JFI submissions under Elsevier Option C: deposits data/code, writes Data Statements, and handles restricted banking data access routes.