From jimf-skills
Plans response-letter strategy for JIMF revision decisions, prioritizing editor-endorsed changes and guiding point-by-point rebuttals with evidence.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jimf-skills:jimf-rebuttalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- A JIMF decision letter arrived: major/minor revision, reject-and-resubmit, or a transfer offer
The editor's letter is the contract, not the referee reports. Read the editor's framing first: which concerns they emphasize, whether they signal the contribution is valued, and what they require versus what is "the referee suggests." At an Elsevier field journal the editor's synthesis governs; a referee's pet request can be respectfully declined if the editor did not endorse it and you give a reason. Sort every comment into: must-do (editor-endorsed or design-critical), should-do (improves the paper, feasible), push-back (wrong, infeasible, or out of scope — answered with evidence), and defer (out of scope for this paper, acknowledged as future work).
| Referee demand | The convincing response |
|---|---|
| "Rule out the global financial cycle" | Add time FE so within-time variation identifies; report the surviving coefficient as a new table |
| "Your surprise is contaminated" | Re-purge the surprise (information-channel correction) and show the before/after |
| "Drop the US / the crisis / use NEER" | Run all three; report point-estimate stability, not just significance |
| "Fix the inference" | Re-estimate with two-way / Driscoll–Kraay / wild bootstrap; report the new SEs |
| "Add policy relevance" | Translate the estimate into a bounded counterfactual (bp of spread, % of GDP of flows) |
| "Extend the country sample / period" | Add it if feasible; if data are restricted, say so honestly and show the sub-sample is representative |
Most JIMF revisions are won on the empirical layer, not the prose: a new exhibit with a number settles a dispute that paragraphs cannot.
The editor reads the opening paragraph of the response before anything else; make it carry the revision. State the two or three substantive changes in plain terms — "we now (i) purge the central-bank information component from the surprise, (ii) add time fixed effects so identification comes from cross-country exposure, and (iii) translate the estimate into basis points of EM spread under a tightening cycle" — and note that the headline result is unchanged (or, honestly, how it changed). A clear summary tells the editor the paper responded seriously before they reach the point-by-point detail, and it frames how every later response should be read.
Referee 1 calls the spillover result "the global financial cycle in disguise"; Referee 2 wants "more for policymakers." The plan: (must-do) add time fixed effects and the openness interaction so within-time variation identifies, killing the GFCy objection, and report the surviving coefficient; (should-do) add a counterfactual that translates the estimate into basis points of EM spread under a tightening cycle, serving Referee 2; (reconcile) tell the editor that the identification fix and the policy translation are the same exhibit viewed two ways. The summary paragraph leads with these two changes.
Not every referee request improves the paper, and a JIMF editor respects a reasoned disagreement. Push back when a check is econometrically wrong (e.g. clustering at a level that mechanically destroys identification), when it is out of scope (a different paper), or when it rests on a misunderstanding you can correct. The form: acknowledge the concern, explain the econometrics or the scope with a citation, offer the defensible alternative you ran instead, and report its result. "We agree cross-country dependence matters; clustering by region as suggested leaves only four clusters, so instead we report Driscoll–Kraay standard errors (new Table A7), which are robust to both serial and cross-sectional dependence; the coefficient is unchanged." A push-back backed by a number and a method reads as competence; a flat refusal reads as defensiveness.
Major revisions at field journals can accumulate requests across rounds. Protect the paper's coherence: implement the must-do changes fully, batch the should-do changes so they do not fragment the argument, and resist letting each round add a section that dilutes the contribution. If two rounds of referee requests are pulling the paper toward a different question, raise it with the editor rather than silently complying — a coherent paper that answers the editor's core concern beats an incoherent one that answers every sentence.
【Journal】Journal of International Money and Finance
【Skill】jimf-rebuttal
【Decision】major / minor / reject-and-resubmit / transfer
【Editor's emphasis】<what the editor required vs. referee-only>
【Comment triage】must-do / should-do / push-back / defer (counts)
【Evidence added】new exhibits answering the lethal comments
【Referee reconciliation】how divergent demands were balanced
【International margin】restated if revision risked domestic drift? [Y/N]
【Deliverable】point-by-point response letter + revised manuscript
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jimf-skillsCreates a prioritized point-by-point rebuttal and revision plan for JMCB decision letters and referee reports. Handles conflicting referee requests and identification/measurement demands.
Structures response letters and revision plans for Journal of Finance revise-and-resubmit submissions. Guides triaging editor and referee points, keeping within page limits, and routing robustness to the Internet Appendix.
Plans and drafts point-by-point rebuttal letters for Journal of Financial Markets R&R decisions, with expert moves for common microstructure objections.