From ectj-skills
Prepares replication packages for The Econometrics Journal: README, software versions, data documentation, seeds, proprietary-data exemptions, and OUP Supporting Information. Use after conditional acceptance or before submission risk review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ectj-skills:ectj-replication-and-data-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this before submission for planning and after conditional acceptance for packaging.
Use this before submission for planning and after conditional acceptance for packaging. Reopen the RES replication policy before final delivery.
For an EctJ methods paper, the replication package should let a referee rerun the claim hierarchy:
00_setup records software versions, seeds, paths, and package checks.01_simulation recreates the minimal Monte Carlo tables used in the paper.02_application recreates the empirical illustration or diagnostic example.03_figures_tables exports exactly the exhibits in the manuscript and supplement.README states expected runtime, hardware assumptions, and which files are slow or optional.If the proof is symbolic rather than computational, still include any scripts used for figures, numerical examples, or robustness checks. Do not leave code that changes a published number outside the package.
Run this audit before treating the package as ready:
For EctJ, the package should make the method credible, not merely archived. A referee should be able to see which computation supports the leading-case theory, which computation supports practical use, and which files are optional robustness material.
Simulation-heavy EctJ papers fail reproduction for reasons pure-empirics packages never face. Verify each before delivery:
Accepted packages appear alongside the article as OUP Supporting Information. Typical shape, hedged where journal practice varies: a top-level README, a master script per claim layer (simulation, application, exhibits), pinned software versions, and data or documented access instructions with ASCII fallbacks for proprietary formats. Exact file-format and size constraints on the OUP side can change; confirm against the journal's current author guidelines before the final upload.
[Replication status] ready / needs fixes / blocked
[Contents] <data/code/README/software/seeds>
[Restricted-data issue] <none, access path, or exemption request>
[Reproduction command] <master script or workflow>
[Publication risk] <low/medium/high and why>
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin ectj-skillsAssembles and audits the code and data deposit for an Econometrica manuscript under the journal's Data and Code Availability Policy, including reproducible Monte Carlo and data provenance.
Builds a data and code replication package for an Economic Journal manuscript to RES/EJ Data Editor standard, including README, data documentation, and Zenodo deposit preparation. Does not run the analysis.
Creates a replication package for Economic Policy manuscripts with one-command reproducibility, data citations, README, and exhibit-to-script mapping. Handles restricted data with synthetic alternatives.