From ier-skills
Anticipates referee objections before submitting an IER manuscript. Maps likely objections by archetype (theory, quantitative, econometric, applied micro, empirical) and advises on pre-emption strategies.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ier-skills:ier-referee-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The paper is near submission and you want to find the objection that would sink it before a referee does
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-derives a known fact" | Perturbation test on the load-bearing assumption; state the failure boundary as a result (ier-theory-model) |
| Structural / quantitative | "Not credibly identified — calibration in disguise"; "counterfactual not policy-invariant" | Sensitivity matrix + untargeted-moment fit + Lucas-critique argument (ier-identification) |
| Econometric method | "What does this buy over the incumbent?"; "no finite-sample evidence" | Head-to-head comparison + Monte Carlo (ier-theory-model, ier-robustness) |
| Applied micro | "Staggered TWFE is biased here"; "exclusion restriction undefended" | Modern DID estimator + clean event study; theory+institutions+falsification for IV (ier-identification) |
| Any empirical | "Is it robust?"; "can it be replicated?" | Threat-mapped robustness + AER-compliant deposit (ier-robustness, ier-replication-package) |
ier-literature-positioning).IER's review is rigor-gated, so the realistic outcomes skew toward "revise to make it correct and general" rather than "reject because not important enough." The desk filter is the first hurdle — the editor decides whether the paper is general-interest enough for IER or belongs at a field journal / an Econometric Society outlet, which is why the cover letter's general-interest framing matters so much. Past the desk, expect referees to drill on the single load-bearing assumption and the identification; a paper that pre-empts those two cleanly converts to an R&R far more often than one that is broad but loose. Process timing and exact desk-reject rates are 待核实 — do not promise the user a timeline.
An author is quietly worried that the headline elasticity is calibrated rather than estimated. The pre-mortem names this as the sink-objection. Rather than hope the referee misses it, the author adds a short subsection showing what data moment would identify the elasticity if estimated, reports the result holds across the calibrated range, and flags in the cover letter that the parameter is set externally for a stated reason with a sensitivity analysis attached. The known weakness is now a controlled, disclosed design choice — the worst it can draw is "please estimate it," which is a survivable R&R comment, not the fatal "calibration in disguise" reject.
At a general-interest journal the first decision is not the referees' — it is the editor's desk decision about whether the paper is general-interest enough for IER, or whether it belongs at a field journal or an Econometric Society outlet. Your cover letter should make that decision easy and correct: in two or three sentences, state the general object that is the contribution, name the two reader segments who care, and (implicitly) draw the sibling boundary. A cover letter that pitches importance like a top-5 submission, or that reads like a field-journal abstract, invites a desk reject or a mis-routing. Treat the cover letter as the editor's filing aid, written in IER's frame of rigor-plus-generality.
A defense placed in an appendix the referee never opens is no defense. For each likely objection, put the answer next to the claim it protects: the assumption defense next to the assumption, the identification argument next to the estimate, the robustness pointer next to the headline result. The pre-mortem is only useful if it changes placement, not just whether the content exists somewhere in the manuscript. An IER referee reading linearly should hit the defense at the moment the doubt arises — that is what converts a potential reject comment into a non-issue.
Audit your paper against its branch's list before the pre-mortem — the soft spot is almost always on it.
【Journal】International Economic Review
【Skill】ier-referee-strategy
【Archetype】theory / structural / method / applied-micro
【Sink-objection】the single objection most likely to reject the paper
【Triage】fix-now / flag-in-cover-letter
【Pre-empts placed】objection → where the defense sits in the text
【Cover letter】general-interest case + sibling boundary drawn? [Y/N]
【Reserve】extra robustness ready for the response (nothing concealed)? [Y/N]
【Verdict】defensible / soft-spot-remains
【Next skill】ier-submission
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin ier-skillsAnticipates and pre-empts referee objections for Economic Journal manuscripts. Focuses on broad interest, identification, and mechanism concerns.
Anticipates objections from European Economic Review referees and maps them to in-paper fixes before submission. Reduces desk-screen risk and pre-empts predictable pushback.
Structures response strategy and revision plan for International Economic Review (IER) decision letters and referee reports. Triages comments into fix/address/costly/misreading buckets.