finman-referee-strategy
Use when pre-empting the objections a Financial Management (FM) referee is likely to raise, before pressing submit — red-teaming the paper from the perspective of an applied-finance reviewer who weighs relevance, rigor, and the "so-what." Anticipates pushback; it does not run the submission preflight (finman-submission) or draft a response to an actual report (finman-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-referee-strategy --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.
# Referee Strategy (finman-referee-strategy) ## When to trigger - The paper feels finished and you want to find the holes before a referee does - You suspect a reviewer will call it "incremental," "a specialist paper," or "rigorous but not interesting" - The identification or sample has a known soft spot you have not yet addressed in the text - You want to write a cover letter that frames the contribution and pre-empts the obvious objections ## How FM referees read a paper An FM referee is an applied-finance academic evaluating against the journal's five criteria — **originality, rigor, timeliness, practical relevance, quality** — and against the brand of papers "people actually read." With **300+ submissions a year and a sub-10% acceptance rate**, the default disposition is rejection, and the fastest paths to it are: *not interesting enough for a general audience*, *belongs in a specialist journal*, *identification not credible*, or *no clear so-what*. Notably, because FM **under-weights trivial robustness**, "you didn't run check X" is rarely fatal unless X addresses a real alternative explanation — so do not over-insure against busywork objections; insure against the four that a
- When to trigger
- How FM referees read a paper
- Red-team the four FM-fatal objections
- The cover letter as a framing instrument
- Building the defense before submission
- Checklist
- Anti-patterns
- What FM's fast process implies for strategy
- Worked vignette (illustrative)
- Referee pushback mapped to the pre-emption
- Output format
What does the finman-referee-strategy skill do?
Use when pre-empting the objections a Financial Management (FM) referee is likely to raise, before pressing submit — red-teaming the paper from the perspective of an applied-finance reviewer who weighs relevance, rigor, and the "so-what." Anticipates pushback; it does not run the submission preflight (finman-submission) or draft a response to an actual report (finman-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill finman-referee-strategy --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.