From jfqa-skills
Plans strategy and structure for a JFQA revise-and-resubmit response, including point-by-point replies, new robustness/identification evidence, and code-archive readiness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jfqa-skills:jfqa-rebuttalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to turn a **JFQA** revise-and-resubmit into an acceptance. The handling **Managing Editor** and the **double-anonymous** referees must see every concern addressed and the contribution sharpened.
Use this skill to turn a JFQA revise-and-resubmit into an acceptance. The handling Managing Editor and the double-anonymous referees must see every concern addressed and the contribution sharpened.
| Comment type | Required artifact | Where it lands |
|---|---|---|
| Identification / endogeneity demand | new design element, placebo, or falsification table | main text, with the old spec moved to the appendix |
| Inference complaint | re-estimated tables under the requested SE scheme | main tables updated; alternates in an Internet Appendix |
| "Economically small" | scaling paragraph (one-SD, %-of-mean, dollar value) | intro and the main-table note |
| Missing rival paper | contrast paragraph plus, if needed, a horse-race column | literature positioning + one exhibit |
| Robustness fishing list | a consolidated robustness table, not ten new tables | Internet Appendix, summarized in one text paragraph |
| "Not interesting / not JFQA" | a reframed contribution case in the editor letter | cover letter; tables alone cannot fix this one |
Triage first, then budget: the identification items consume most of the calendar; the scaling and citation items are cheap and should never be the reason a deadline slips.
Referee: "Clustering by firm only likely understates the standard errors given common time shocks." Model response: agree without hedging; re-estimate every main table with two-way firm-and-year clustering; report that the headline t-statistic moves from 4.2 to 3.1 and the conclusion stands; add a wild-cluster-bootstrap panel as Internet Appendix Table IA.3 for the specifications with few clusters; end with the exact page and table numbers where the manuscript changed. The reply quotes the comment in full, leads with the new result rather than the rhetoric, and gives the referee a checkable location for every claim.
【Editor letter】main changes summarized? [Y/N]
【Per-referee】every comment quoted + answered + located? [Y/N]
【New evidence】identification/robustness/magnitude added where asked? [Y/N]
【Reproducible】new analyses in the master script? [Y/N]
【Anonymized】revised PDF + metadata clean? [Y/N]
【Next step】resubmit via Editorial Manager
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jfqa-skillsStructures 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.
Drafts structured response letters for JFE revise-and-resubmits: cover note, point-by-point replies, and revision map. Use after revisions are done.
Guides response to a Journal of Banking & Finance revise-and-resubmit: triage referee comments by priority, strengthen identification, add robustness checks, preserve anonymity, and draft a point-by-point response letter with standard JBF fixes.