jbf-replication-and-data-policy
Use when preparing the required data statement, code archive, repository deposit/link, and proprietary-data documentation for a Journal of Banking & Finance manuscript under Elsevier Option C research-data expectations.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbf-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 (jbf-replication-and-data-policy) ## When to trigger - The paper uses CRSP, Compustat, BankFocus, Dealscan, TRACE, Call Reports, hand-collected data, or simulations - You need a data availability statement for Elsevier/JBF submission - You want a legal and useful replication package despite proprietary data ## Policy stance JBF follows Elsevier **Option C** research-data instructions. At submission, authors must state data availability. For shareable data, deposit the research data in a relevant repository and cite/link it in the article. If data cannot be shared, state why (for example, proprietary, sensitive, confidential, or licensing limits). JBF does not operate a dedicated journal-run replication archive, so the practical package should combine a repository deposit where rights allow, code, metadata, and a precise access route for restricted inputs. ## Package structure ```text README.md data_access/ # licensed-data instructions, not raw proprietary files code/ 00_setup.* 01_build_sample.* 02_main_tables.* 03_figures.* 04_robustness.* output/ tables/ figures/ requirements.* # renv.lock / requirements.txt / Stata package list ``` ## Data availabilit
- When to trigger
- Policy stance
- Package structure
- Data availability statements
- Code expectations
- Proprietary-data audit
- Source-by-source sharing matrix
- Worked statement draft (illustrative)
- Pre-submission package audit
- Editor pushbacks on data
- Output format
What does the jbf-replication-and-data-policy skill do?
Use when preparing the required data statement, code archive, repository deposit/link, and proprietary-data documentation for a Journal of Banking & Finance manuscript under Elsevier Option C research-data expectations.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbf-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.