From jfi-skills
Prepares research-data materials for JFI submissions under Elsevier Option C: deposits data/code, writes Data Statements, and handles restricted banking data access routes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jfi-skills:jfi-replication-and-data-policyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Preparing data/code materials before submitting or at acceptance
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:
[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.
| Data tier | Typical examples | What you can realistically share |
|---|---|---|
| Public | Call Reports, HMDA, FDIC Summary of Deposits | Full data plus code — deposit everything |
| Commercial license | DealScan, Orbis/Bankscope, branch-rate databases | Code, construction steps, and access instructions; never raw data |
| Supervisory / central-bank | Credit registers, FR Y-14, examination data | Code, variable definitions, the application route, and cleared aggregates |
For the supervisory tier, the Data Statement should name the granting institution and the access route so a referee believes replication is possible in principle — credibility matters disproportionately at a venue where the best identification lives inside restricted registers. Repository specifics and any evolving Elsevier requirements: confirm against the journal's current author guidelines.
Data statement: Loan-level records are from the [country] credit register,
accessed on-site under agreement [ref]; they cannot leave the central bank.
We deposit: (i) all construction and estimation code; (ii) variable
definitions and sample filters; (iii) bank-level aggregates cleared for
release; (iv) instructions for applying for register access. Public inputs
(Call Reports, HMDA) are included in the repository. Datasets are cited
with [dataset] tags in the reference list.
[dataset] reference tag【Data Statement】drafted, access conditions stated? [Y/N]
【Deposit / explain】repository chosen and linked in EM, or restriction explained? [Y/N]
【[dataset] tags】data cited in references? [Y/N]
【Restricted data】access route + shareable code noted? [Y/N]
【Note】Option C applies; no JFI-specific archive is named
【Next skill】jfi-review-process
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jfi-skillsGenerates a JBF/Elsevier Option C replication package with data availability statement, code archive structure, and proprietary-data access documentation for banking/finance manuscripts.
Prepare data-availability statements and code/data archives for Journal of Corporate Finance submissions under Elsevier Research Data Option C.
Prepares code and data archives required by the JFQA Code Sharing Policy for accepted post-2024 submissions. Builds source code, datasets, and read-me for deposit in the JFQA Dataverse.