From jde-skills
Assembles a JDE-compliant replication package (data, code, README, pinned environment) for submission or acceptance. Does not run the analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jde-skills:jde-replication-and-data-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- A paper is heading toward submission or acceptance and the replication package is not built
JDE operates a mandatory replication policy. The journal will, in general, publish a paper only if the data used are clearly and precisely documented and readily available to any researcher for replication. Authors of accepted papers containing empirical, simulation, or experimental work must provide, prior to publication, the data, programs, and other computational details sufficient to permit replication; these are posted on the JDE website alongside the article. JDE partners with Mendeley Data to host research data, displayed next to the article on ScienceDirect.
Crucially, this is not only an acceptance-stage formality: editors or referees may request the data, programs, and computational details at the review stage. So the package must be submission-ready, not assembled after acceptance.
run_all) that regenerates every table and figure from raw or constructed data, in order.ssc/net versions, renv.lock, or requirements.txt; set and report all random seeds (bootstrap, randomization inference, simulation).JDE's standard is that data be available for replication, but development work often uses restricted government surveys or partner-collected data that cannot be redistributed. In that case:
For pre-results-reviewed papers, the pre-specified research plan (hypotheses, statistical analysis plan, power analysis) is included in the supplementary online appendix, and the published article carries a footnote noting the pre-results submission — the analysis plan is itself part of the replication record.
| Data in the paper | What the JDE package must contain |
|---|---|
| Author-collected RCT survey data | De-identified microdata + master script + survey instruments |
| Government microdata under DUA | All programs + a documented access path + a synthetic test extract |
| Partner-NGO administrative records | Programs + access contact + the construction code, data withheld |
| Public secondary data (DHS, World Bank) | Download script or pinned snapshot + every cleaning step |
Hypothetical: a cluster-randomized microfinance experiment whose endline consumption data are de-identifiable but whose credit-bureau linkage is restricted.
run_all.do regenerates all 6 tables and 4 figures in order; /raw holds the de-identified survey panel; /restricted_README.md gives the bureau access path and the contact; seeds for the randomization-inference p-values are set and printed.【Master script regenerates all exhibits?】[Y/N]
【README】provenance + steps + versions + seeds? [Y/N]
【Environment pinned】[Stata/R/Python versions]
【Data status】public / restricted (+ access path)
【Mendeley Data deposit prepared?】[Y/N]
【Pre-results plan in appendix?】[Y/N/NA]
【Next step】jde-review-process
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jde-skillsBuilds a JIE-compliant replication deposit (code, data, master script, README) for an international-economics manuscript. Does not run the analysis.
Assembles the data-and-code replication package for a REStat manuscript, including deposit to the REStat Harvard Dataverse with a replication-permitting README.
Guides authors of accepted JOLE papers through assembling a data/code deposit for the JOLE Dataverse Repository, including proprietary-data handling and the AER data-availability policy.