Agent skill · Code Review & Quality

rfs-referee-strategy

Use when choosing suggested/opposed referees or running an objection pre-mortem before submitting a The Review of Financial Studies (RFS) manuscript. Anticipates reviewer concerns; does NOT write the rebuttal (that is rfs-rebuttal).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rfs-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: Review-of-Financial-Studies-Skills/skills/rfs-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 & Objection Pre-Mortem (rfs-referee-strategy) ## When to trigger - The portal asks for suggested and opposed reviewers - You want to anticipate the objections RFS referees will raise before they do - A coauthor asks "who will referee this and what will they hate?" - Preparing the cover letter's referee section ## Two jobs: referee selection and objection pre-mortem ### A. Suggesting and opposing referees - **Suggest** referees who are active in your exact sub-field, have published the closest methods, and can evaluate both the novelty and the rigor. RFS referees are usually the authors you cite most. - Aim for a balanced slate: not only your closest collaborators' circle, and not only theorists for an empirical paper (or vice versa). - **Oppose** referees only with a brief, professional reason (active competing project, prior dispute, direct conflict). Do not over-exclude — editors notice and discount long oppose lists. - Never suggest coauthors, advisors/advisees, or same-institution colleagues — these are conflicts the editor will strike. - **Do not suggest a current RFS editor as a referee.** Know who handles your area (e.g., Viral Acharya, Xavier Giroud, Andr

What's inside
Steps it walks through
  1. When to trigger
  2. Two jobs: referee selection and objection pre-mortem
  3. A. Suggesting and opposing referees
  4. B. Objection pre-mortem (the high-value step)
  5. Reading the desk-reject vs. send-out signal
  6. Cover-letter referee note
  7. Checklist
  8. Anti-patterns
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the rfs-referee-strategy skill do?

Use when choosing suggested/opposed referees or running an objection pre-mortem before submitting a The Review of Financial Studies (RFS) manuscript. Anticipates reviewer concerns; does NOT write the rebuttal (that is rfs-rebuttal).

How do I install it?

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