Individual skill
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).
Financial-Management-Skills/skills/finman-referee-strategy/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- finance Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,147 bytes
Read excerpt
# 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 actually sink papers here. The editors aim for a **median 6–8 week turnaround**, so reports tend to be focused; a paper that telegraphs its contribution and pre-empts the live concerns reads as ready.
## Red-team the four FM-fatal objections