From jbes-skills
Structures a response letter and revision strategy for a JBES R&R or major revision decision. Triages referee comments by priority and routes analysis to the relevant jbes-* skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jbes-skills:jbes-rebuttalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- A JBES decision letter arrived: revise-and-resubmit or major revision
JBES is run by a panel of Co-Editors / Joint Editors, and the handling Co-Editor's letter sets priorities — read it first and let it rank the referees' points. Because JBES referees are method experts, their objections cluster on three axes: statistical validity (assumptions, asymptotics, inference), empirical relevance (the application, whether the method truly helps it), and reproducibility (can the simulation and empirical results be regenerated). Treat an R&R as a near-final opportunity: resolve everything substantive in this round.
jbes-identification-strategy; simulations/application → jbes-data-analysis; reproducibility → jbes-replication-and-data-policy; exposition → jbes-writing-style. Do the work, update exhibits, then write the letter.A hypothetical JBES R&R on a new spectral test for structural breaks in volatility draws three reports (numbers illustrative). The handling Co-Editor's letter underscores Referee 1's validity point and flags the application as thin. Triage: Referee 1 ("the null limiting distribution assumes no leverage effect") is fundamental — route to jbes-identification-strategy, then settle it with a new Monte Carlo showing an illustrative size of 5.1% under a leverage DGP. Referee 2 ("compare to the CUSUM-of-squares benchmark") is fundamental on evidence — route to jbes-data-analysis and add the benchmark in the same tables. Referee 3 ("dense notation") is clarification — route to jbes-writing-style. The reproducibility comment goes to jbes-replication-and-data-policy. The manuscript is updated first; only then is the letter written, each response citing the exact theorem/table/page.
| JBES report objection | Fix this skill enforces |
|---|---|
| "The validity claim is still unproven." | Settle it with a decisive new Monte Carlo rather than prose argument |
| "You promised this for future work." | Do the theory/simulation/application this round; an R&R is near-final |
| "Where in the paper did you change this?" | Cite the exact section/theorem/table/figure/page in each response |
Calibration anchor (hedged): the handling Co-Editor's letter is the contract — a point the editor underscores is binding, one only a single referee raised and the editor did not flag is lower priority (still answered). For the number and scope of revision rounds, follow the decision letter's own instructions.
【Decision】R&R / major revision
【Co-Editor's binding points】[...]
【Classification】fundamental: [...] / clarification: [...] / disagreement: [...]
【Routed to】jbes-identification-strategy / jbes-data-analysis / jbes-replication-and-data-policy (as needed)
【Letter status】point-by-point with locations? [Y/N]
【Tone check】gracious + concrete? [Y/N]
【Next step】resubmit via the JBES portal (jbes-submission for file checks)
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jbes-skillsDrafts response-to-referees letters and revision plans for REStat decision letters. Structures point-by-point replies, triages comments, and flags identification/measurement objections.
Plans a response-to-referees strategy for JEBO decision letters: triaging comments, ordering concessions vs pushback, scoping new experimental treatments, and structuring the point-by-point rebuttal letter.
Structures response strategy and letter for QJE R&R or reject-and-resubmit decisions. Prioritizes referee comments and guides revision sequencing.