jfi-replication-and-data-policy
Use when preparing the research-data materials a Journal of Financial Intermediation (JFI) submission expects under Elsevier Option C — deposited, cited, and linked research data where possible; an explanation where sharing is impossible; a Data Statement; [dataset]-tagged references; and a credible access route for restricted supervisory or credit-register data. It prepares the package; it does not deposit for you.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfi-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 (jfi-replication-and-data-policy) ## When to trigger - Preparing data/code materials before submitting or at acceptance - Writing the Data Statement or handling restricted/proprietary banking data ## What JFI actually requires (verified 2026-06-20; re-confirm on the official page) JFI follows Elsevier **Option C** for research data. Research data here includes **software, code, models, algorithms, protocols, and methods** — not just datasets. Authors are required to: - **Deposit research data in a relevant repository and cite/link it**, or explain why data cannot be shared. - Provide a **Data Statement** on data availability when relevant; it is supported in the submission flow and published with the article. - Cite datasets in the text and reference list using the **`[dataset]` tag**. Crucially, JFI has **no journal-specific mandatory replication-code archive** — there is no equivalent of the Journal of Applied Econometrics Data Archive or the American Economic Review replication mandate. Do not invent a JFI-only archive requirement, but do treat deposit/cite/link-or-explain as the live Elsevier data-policy obligation. ## How to prepare - **Empirical pa
- When to trigger
- How to prepare
- Restricted banking data: the disclosure ladder
- Worked Data Statement skeleton (credit-register paper, illustrative)
- Friction points editors and referees raise
- Anti-patterns
- Output format
What does the jfi-replication-and-data-policy skill do?
Use when preparing the research-data materials a Journal of Financial Intermediation (JFI) submission expects under Elsevier Option C — deposited, cited, and linked research data where possible; an explanation where sharing is impossible; a Data Statement; [dataset]-tagged references; and a credible access route for restricted supervisory or credit-register data. It prepares the package; it does not deposit for you.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfi-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.