Agent skill · Data & Analytics

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.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
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.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Review-of-Finance-Skills/skills/rof-replication-and-data-policy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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

What's inside
Steps it walks through
  1. Package checklist
  2. RoF replication packet
  3. OUP supplementary package blueprint
  4. Finance-data shipping reality
  5. Vintage and version control
  6. Pre-acceptance dry run
  7. Worked exception case
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
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.

Keep going