Agent skill · Data & Analytics

mathfin-replication-and-data-policy

Use when preparing Wiley data availability statements and reproducibility notes for a Mathematical Finance manuscript — covers the no-data case typical of this theory venue, archives for illustrative numerical code, per-exhibit provenance, and what a proofs journal does and does not require of authors.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mathfin-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: 5 KB
Bundled scripts: none
Path: Mathematical-Finance-Skills/skills/mathfin-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

# Replication & Data Policy (mathfin-replication-and-data-policy) ## When to trigger - The manuscript needs a Data Availability Statement - Numerical experiments, simulations, or code accompany the theory - The paper uses no data and you need the correct statement ## Policy stance Wiley policy expects all research- and synthesis-based articles to include a Data Availability Statement. For this journal, that often means using Wiley's theory/no-new-data template. There is no journal-specific mandatory replication archive comparable to empirical economics/finance data archives, but code for numerical illustrations should be reproducible when included. ## Statement templates ### No data ```text Data availability statement: Data sharing is not applicable to this article as no datasets were generated or analysed during the current study. ``` ### Numerical code only ```text Data availability statement: The numerical code used to generate the illustrative figures/tables is available at [repository/DOI]. No proprietary empirical data were used. ``` ### Public data, if unusually used ```text Data availability statement: The data are publicly available from [source] at [URL]. The code used fo

What's inside
Steps it walks through
  1. When to trigger
  2. Policy stance
  3. Statement templates
  4. No data
  5. Numerical code only
  6. Public data, if unusually used
  7. Reproducibility checklist
  8. Numerical-experiment package
  9. Exhibit provenance ledger
  10. Boundaries of this venue's policy
  11. Minimal-footprint rule
  12. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the mathfin-replication-and-data-policy skill do?

Use when preparing Wiley data availability statements and reproducibility notes for a Mathematical Finance manuscript — covers the no-data case typical of this theory venue, archives for illustrative numerical code, per-exhibit provenance, and what a proofs journal does and does not require of authors.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mathfin-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