Agent skill · Code Review & Quality

jf-referee-strategy

Use when anticipating referee objections and selecting suggested/opposed reviewers before or during a The Journal of Finance (JF) submission. Plans for review; it does not write the rebuttal (use jf-rebuttal).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jf-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: 6 KB
Bundled scripts: none
Path: Journal-of-Finance-Skills/skills/jf-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 (jf-referee-strategy) ## When to trigger - Before submitting: anticipating the objections a JF referee will raise - The portal asks for suggested / opposed reviewers - A conflict of interest among editors, AEs, or referees needs flagging ## How JF review works (plan around it) JF, the AFA flagship, runs a demanding multi-round process: a handling **editor** (currently **Antoinette Schoar (MIT)**, with co-editors and 50+ Associate Editors — verify the masthead) screens first, then assigns typically **2–3 referees**. The reality is severe — **~33–45% desk-rejected, ~5% accepted** (afajof.org editor reports, accessed 2026-05-30). Most papers die at desk review, so the first job is surviving the editor, not the referees. ### JF-specific channels - A **cover letter is normally unnecessary** at JF — use one **only** to flag a conflict of interest (referees/AEs/editors who should be excluded) or to request a code-sharing exemption. Do not pad it (see `jf-submission`). - Suggested/opposed reviewers, if the portal asks, should be specific and justified. ## Anticipating objections (pre-empt in the paper) | Likely referee objection | Where to neutralize it | |--------------

What's inside
Steps it walks through
  1. When to trigger
  2. How JF review works (plan around it)
  3. JF-specific channels
  4. Anticipating objections (pre-empt in the paper)
  5. Reading the AFA screening funnel
  6. Desk-reject patterns at a top-3 finance journal
  7. Worked vignette — pre-empting the panel on an anomaly paper
  8. Referee-pushback patterns and the JF-specific fix
  9. Checklist
  10. Anti-patterns
  11. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jf-referee-strategy skill do?

Use when anticipating referee objections and selecting suggested/opposed reviewers before or during a The Journal of Finance (JF) submission. Plans for review; it does not write the rebuttal (use jf-rebuttal).

How do I install it?

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