Agent skill · Business & Finance

jfm-referee-strategy

Use when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of the report. Anticipates and triages; it does not invent evidence or citations.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jfm-referee-strategy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Path: Journal-of-Financial-Markets-Skills/skills/jfm-referee-strategy/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

# Referee Strategy (jfm-referee-strategy) ## When to trigger - Pre-submission: you want to surface the objections a microstructure insider will raise before they do - A report arrived and you need to triage which comments are fatal, fixable, or push-back - You suspect the referee will challenge measurement or endogeneity rather than the idea - You need to estimate whether the asks are within an R&R's reach or signal a reject - The editor's letter prioritizes some comments and you must read the signal ## The objections JFM referees actually raise A JFM referee is a microstructure specialist. The predictable lines of attack cluster, and most live in measurement and identification, not novelty. | Referee line | What they really doubt | Pre-empt with | |--------------|------------------------|---------------| | "This is not really microstructure" | the mechanism is broad finance | `jfm-topic-selection` framing; lead with the trading-process object | | "The result is driven by the liquidity measure" | measurement artifact | `jfm-empirical-design` + alternative constructs in `jfm-robustness` | | "Liquidity is endogenous here" | reverse causality / confounding | `jfm-identification`: a ma

What's inside
Steps it walks through
  1. When to trigger
  2. The objections JFM referees actually raise
  3. Running the pre-mortem and the triage
  4. Timing the pre-mortem
  5. Worked pre-mortem (illustrative)
  6. Reading the decision letter
  7. The two reviewer profiles to plan for
  8. Checklist
  9. What a microstructure referee rewards, beyond catching flaws
  10. Anti-patterns
  11. Estimating whether an R&R is reachable
  12. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jfm-referee-strategy skill do?

Use when anticipating the microstructure referee's objections for a Journal of Financial Markets (JFM) manuscript — a pre-submission pre-mortem and, post-decision, a triage of the report. Anticipates and triages; it does not invent evidence or citations.

How do I install it?

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

Keep going