From rof-skills
Guides preparation of RoF replication packages: code, pseudo-datasets for proprietary sources, logs, Data Availability Statement, dataset citations, and OUP supplementary hosting per journal policy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rof-skills:rof-replication-and-data-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this before submission and after acceptance. Reopen the current RoF code-sharing and
Use this before submission and after acceptance. Reopen the current RoF code-sharing and data-availability policy before final packaging.
Build the packet around editorial risk:
README states execution order, software, package versions, expected runtime, and output locations.data_manifest names every raw, intermediate, pseudo, and restricted dataset, with access status.run_all recreates each table, figure, and appendix exhibit or clearly marks non-runnable restricted
steps.logs prove that the submitted outputs were generated from the submitted programs.DAS and dataset citations match the manuscript, cover letter, and supplementary files.For proprietary data, the pseudo-dataset is not decoration. It should let the editor see variable names, file structure, merge keys, and code flow, while logs or other evidence document the confidential run. Request exceptions at the earliest required stage; late exceptions create publication risk.
rof_replication/
README.md run order, software + versions, runtime, output map
data/raw/ non-proprietary inputs only, with dataset citations
data/pseudo/ simulated rows mirroring restricted files (schema-true)
code/01_build cleaning: return screens, merges, winsorizing
code/02_main every body table and figure, numbered as in the paper
code/03_appendix internet-appendix exhibits
logs/ full execution logs from the confidential run
output/ regenerated exhibits, traceable to the submitted PDF
| Source | Ships in the package? | What ships instead |
|---|---|---|
| CRSP / Compustat (WRDS) | No — licensed | exact query, extraction date, variable list, pseudo-rows |
| Datastream / Refinitiv | No | request scripts, screen list incl. dead-stock handling, pseudo-data |
| Bankscope / Orbis (BvD) | No; vintages also vanish | vintage date, consolidation filters, ID list if the license allows |
| ECB SDW / Eurostat | Usually yes | series codes plus download date, or the snapshot itself |
| Hand-collected (filings, prospectuses) | Yes — expected | the dataset plus the collection protocol |
| Proprietary (exchange, supervisor, bank) | No | pseudo-dataset, logs, access procedure, exception named in the cover letter |
Confirm the current shipping rules for each source against the journal's current author guidelines and your own license terms before promising anything in the DAS.
output/; anything untraceable is
either a stale exhibit or a missing script.Illustrative. A microstructure paper combines proprietary order-book data from a European exchange with public Datastream prices. The packet ships: complete code; a pseudo order-book with the true schema and fabricated quantities; logs from the confidential run; Datastream request scripts; a cover-letter paragraph requesting the exception at initial submission — the stage RoF requires — citing the exchange's redistribution restriction; and a DAS routing readers to the exchange's access procedure. Publication then waits only on packet verification, not a post-acceptance scramble. Verify the exact exception mechanics against the journal's current author guidelines.
[Replication status] ready / needs fixes / exception needed
[Data status] public / proprietary / restricted / simulated
[Code status] complete / missing pieces / undocumented
[DAS] <draft or missing>
[Publication risk] <low/medium/high>
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin rof-skillsGenerates a JBF/Elsevier Option C replication package with data availability statement, code archive structure, and proprietary-data access documentation for banking/finance manuscripts.
Prepares 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.
Assembles the data-and-code replication package for a REStat manuscript, including deposit to the REStat Harvard Dataverse with a replication-permitting README.