Agent skill · Code Review & Quality

ier-referee-strategy

Use when anticipating referee objections before submitting an International Economic Review (IER) manuscript, or when reading the room of an IER review. Maps the likely objections by archetype and pre-empts them; it does not draft the response letter (see ier-rebuttal).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ier-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: 8 KB
Bundled scripts: none
Path: International-Economic-Review-Skills/skills/ier-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 (ier-referee-strategy) ## When to trigger - The paper is near submission and you want to find the objection that would sink it before a referee does - You are deciding what to put in the paper vs. hold in reserve for the response - A draft is strong but you suspect one undefended assumption or one fragile number is the soft spot - You want to calibrate expectations for IER's review (a rigor-gated, theory-leaning process) ## How IER referees read An IER referee is usually a rigor-minded economist who reads for **whether the contribution is correct, general, and tightly linked to its evidence**. Unlike a top-5 referee, they are not primarily asking "is this important enough"; they are asking "is this right, and does it teach a general lesson." The most common reasons an IER paper stalls are: an undefended load-bearing assumption, identification that is "calibration in disguise," a headline number that moves under a reasonable perturbation, or a proof that is not airtight. Pre-empt by archetype: | Archetype | The objection that sinks it | Pre-empt by | |-----------|-----------------------------|-------------| | Pure / applied theory | "The result is knife-edge / re-

What's inside
Steps it walks through
  1. When to trigger
  2. How IER referees read
  3. The pre-mortem routine
  4. Calibrating expectations for an IER review
  5. Worked example (illustrative)
  6. The cover letter does the desk editor's filing for them
  7. Pre-empt where the referee looks, not where it is convenient
  8. Checklist
  9. Anti-patterns
  10. Branch-specific soft spots to audit before submitting
  11. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ier-referee-strategy skill do?

Use when anticipating referee objections before submitting an International Economic Review (IER) manuscript, or when reading the room of an IER review. Maps the likely objections by archetype and pre-empts them; it does not draft the response letter (see ier-rebuttal).

How do I install it?

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