Agent skill · Code Review & Quality

mathfin-review-process

Use when navigating the Mathematical Finance (Wiley) review process — single-blind editor screening, associate-editor handling, and referees who verify proofs line by line. Explains what reviewers at this theory venue check first, common desk-screen failure patterns for theorem-first papers, and how to read review-stage signals.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mathfin-review-process --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-review-process/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

# Review Process (mathfin-review-process) ## When to trigger - Before submission, to understand the editor and referee lens - After submission, to interpret review-stage status - When deciding whether a theorem-first paper is ready for this journal ## Process facts The accessible Wiley author-guideline text identifies **single-blind peer review**: the editor screens submissions, suitable papers may be assigned to an Associate Editor, outside referees may be consulted, and the Associate Editor prepares a recommendation. The current Wiley product-page metadata checked on 2026-06-20 lists Rama Cont as editor; reopen the live product or editorial-board page before naming the editor in advice to an author. ## What reviewers evaluate - Methodological novelty in financial mathematics - Contribution to financial modelling, not only mathematical difficulty - Correctness and self-contained completeness of proofs - Precision of assumptions and notation - Whether numerical experiments support theory rather than substitute for it - Fit with the journal's stochastic-analysis and financial-modelling audience ## Desk-risk triggers - Routine computational application to financial data - Missing pro

What's inside
Steps it walks through
  1. When to trigger
  2. Process facts
  3. What reviewers evaluate
  4. Desk-risk triggers
  5. What a Mathematical Finance referee reads first
  6. Desk-screen failure patterns for theory submissions
  7. Reading the silence
  8. Reviewer packet
  9. Decision vocabulary at this venue
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the mathfin-review-process skill do?

Use when navigating the Mathematical Finance (Wiley) review process — single-blind editor screening, associate-editor handling, and referees who verify proofs line by line. Explains what reviewers at this theory venue check first, common desk-screen failure patterns for theorem-first papers, and how to read review-stage signals.

How do I install it?

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