From jmcb-skills
Organizes online appendix content for JMCB manuscripts, deciding what goes in main text vs appendix and structuring the replication path.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jmcb-skills:jmcb-internet-appendixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The main text is over the recommended 40 pages and material must move out without losing the argument
JMCB explicitly excludes the online appendix from the recommended 40-page limit (检索于 2026-06;以官网为准), which makes the appendix the pressure valve for a tight main text — but the journal's replication heritage means the appendix is also where verifiability lives. The discipline is twofold: the main text must remain self-contained (a reader who never opens the appendix still believes the result), and the appendix must map cleanly back (every appendix table answers a question the main text raised). Material that is load-bearing for the headline belongs in the body; material that supports or verifies belongs in the appendix.
| Material | Main text | Online appendix |
|---|---|---|
| Headline IRF / table / counterfactual | ✓ | |
| The 3–4 load-bearing robustness checks | ✓ | |
| Model derivations, proofs, full FOCs | ✓ | |
| Full robustness battery (alternative orderings, windows, definitions) | summary row | ✓ full set |
| Data construction detail, variable crosswalks, M&A handling | brief note | ✓ full |
| Additional sample splits and heterogeneity cuts | key cut | ✓ rest |
| Estimation diagnostics (convergence, multi-start, Monte Carlo recovery) | one line | ✓ |
A well-organized appendix earns goodwill; a sprawling one frustrates the referee who has to mine it.
Because JMCB's own archive history is part of the field's collective memory about reproducibility, treat the data/code plan as a first-class deliverable, not an afterthought. Decide, before submission, exactly which inputs are public (Call Reports, Y-9C, FRED/ALFRED vintages) and which are restricted, and write the access path for the restricted ones (RDC, central-bank data room, credit register, with the application route). If a step in the construction is non-obvious — a splice across a regime break, an M&A crosswalk, a winsorization rule — it belongs in the appendix in enough detail to rebuild. A referee who can see exactly how to reproduce the public part and exactly how to request the restricted part is far more likely to trust the result.
Authors sometimes use the appendix to bury a check that did not go their way. JMCB referees read the appendix precisely to find what the body omits, so a failed or weakened result discovered there reads far worse than one reported honestly in the main text. The rule: if a result qualifies the headline, it belongs in the body with interpretation; the appendix is for material that supports or verifies, never for material that quietly contradicts. Transparency in the body, depth in the appendix.
A monetary-transmission paper runs 18 robustness specifications and a 12-page model derivation, blowing past the 40-page recommendation. The fix: keep the headline IRF, the heterogeneity-by-capital cut, and the two checks that defuse the shock-contamination and demand objections in the body (under the page cap), and move the full derivation, the other 16 robustness runs, the RSSD merger crosswalk, and the convergence diagnostics to the online appendix — each section opening with one sentence tying it to a main-text claim. The body is now self-contained at ~38 pages, and a referee can verify any step by appendix section number. The data section states which inputs are public and documents the supervisory-panel access path for the restricted one.
【Journal】Journal of Money, Credit and Banking
【Skill】jmcb-internet-appendix
【Self-contained?】main text holds without the appendix? [Y/N]
【Moved to appendix】derivations / full robustness / data construction / extra cuts
【Stayed in body】headline + load-bearing checks
【Appendix→main map】each appendix table tied to a main-text claim? [Y/N]
【Replication plan】code/data deposit; data-exemption + access path if restricted
【Next skill】jmcb-writing-style
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jmcb-skillsOrganizes the journal-hosted Internet Appendix for a Journal of Financial Economics (JFE) manuscript: moves content off main text, cross-references, and keeps appendix self-contained.
Allocates content between main text and Internet Appendix for Journal of Finance manuscripts, following JF's actual policy on submission format, page limits, and self-containment.
Assembles Internet Appendix, data codebook, and replication materials for a JFM manuscript. Organizes main text vs. appendix content and documents TAQ/proprietary-data access path.