jcf-replication-and-data-policy
Use when preparing the data-availability statement and code/data archive for a Journal of Corporate Finance (JCF) submission under Elsevier "Research Data" Option C — stating data availability at submission and depositing or explaining why data cannot be shared. It builds the data/code deliverables; it is not a substitute for vendor-license compliance.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-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.
# Replication & Data Policy (jcf-replication-and-data-policy) ## When to trigger - Drafting the **data-availability statement** at submission - Deciding what code/data to deposit and where, given vendor licenses - Preparing the archive that supports the paper's tables and figures ## JCF data policy (verified; re-confirm on the official guide) JCF follows **Elsevier "Research Data" Option C**. Authors are **required to state data availability at submission** and are **encouraged to deposit research data — including software, code, models, and algorithms — in a relevant repository** and cite/link it, or provide a statement explaining why the data cannot be shared. There is **no dedicated JFE-Data-Archive-style mandatory replication-package mandate** for JCF (待核实 / none found): the policy is the standard **Elsevier data-availability-statement** framework, **not** a finance-society mandatory code/data archive. ## What this means in practice - Most JCF data come from **licensed vendors** (Compustat, CRSP, SDC/Refinitiv, DealScan, BoardEx, ISS, Execucomp). You **cannot** redistribute the raw data. - For licensed data, share **code + variable-construction details + access instructions**,
- When to trigger
- JCF data policy (verified; re-confirm on the official guide)
- What this means in practice
- Build checklist
- Source-by-source sharing decisions
- Worked statement: mixed licensed and hand-collected inputs
- Archive skeleton that survives a JCF revision
- Anti-patterns
- Output
What does the jcf-replication-and-data-policy skill do?
Use when preparing the data-availability statement and code/data archive for a Journal of Corporate Finance (JCF) submission under Elsevier "Research Data" Option C — stating data availability at submission and depositing or explaining why data cannot be shared. It builds the data/code deliverables; it is not a substitute for vendor-license compliance.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcf-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.