rof-replication-and-data-policy
Use when preparing the Review of Finance (RoF) replication package — code, data, pseudo-datasets for proprietary sources such as Datastream or Bankscope, log files, the Data Availability Statement, dataset citations, cover-letter exception requests at initial submission, and OUP supplementary hosting, since the journal's code-sharing policy can hold publication until programs are received.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rof-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.
# Review of Finance Replication And Data Policy Use this before submission and after acceptance. Reopen the current RoF code-sharing and data-availability policy before final packaging. ## Package checklist - Prepare replication programs with comments, software names, versions, package dependencies, and execution order. - Provide actual data when non-proprietary. If data are proprietary, prepare a pseudo-dataset plus log files or other evidence required by current policy. - Draft a Data Availability Statement and formatted dataset citations. - Request any exception in the cover letter at initial submission when policy requires early disclosure. - Expect publication to wait until code is received when the policy applies. - Package materials for OUP supplementary hosting rather than inventing a separate archive. ## RoF replication packet 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 step
- Package checklist
- RoF replication packet
- OUP supplementary package blueprint
- Finance-data shipping reality
- Vintage and version control
- Pre-acceptance dry run
- Worked exception case
- Output format
What does the rof-replication-and-data-policy skill do?
Use when preparing the Review of Finance (RoF) replication package — code, data, pseudo-datasets for proprietary sources such as Datastream or Bankscope, log files, the Data Availability Statement, dataset citations, cover-letter exception requests at initial submission, and OUP supplementary hosting, since the journal's code-sharing policy can hold publication until programs are received.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rof-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.