Agent skill · Data & Analytics

jmcb-identification

Use when the identification argument is the bottleneck for a Journal of Money, Credit and Banking (JMCB) manuscript — macro shock identification (SVAR, narrative, sign/high-frequency monetary surprises), parameter identification in a monetary/banking model, or a micro-banking causal design. Stress-tests the data-to-object mapping to the JMCB bar before exhibits are finalized.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmcb-identification --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 10 KB
Bundled scripts: none
Path: Journal-of-Money-Credit-and-Banking-Skills/skills/jmcb-identification/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Identification Strategy (jmcb-identification) ## When to trigger - A monetary-policy "shock" is just a residual from a regression, with no defense against the information effect - An SVAR's ordering / sign restrictions are unstated or unmotivated by theory - A bank/loan-level causal claim rests on OLS + controls, or TWFE on staggered regulation - A banking-model parameter is "calibrated" with no statement of what in the data pins it - You are unsure the identification clears JMCB's policy-relevant, mechanism-explicit bar ## The JMCB identification bar JMCB referees are monetary/banking economists who judge identification by **whether the data-to-object mapping is explicit, theory-disciplined, and robust to the field's known critiques**. Because the journal spans macro and micro, "identification" means different things by engine — pick the engine and make the argument transparent, with timing and institutions on the page. The dominant failure mode JMCB punishes is a "shock" or "treatment" that is not exogenous to the thing it is supposed to move. ## Branch paths ### Branch A: Macro shock identification (SVAR / narrative / external instruments) - **High-frequency monetary surprises

What's inside
Steps it walks through
  1. When to trigger
  2. The JMCB identification bar
  3. Branch paths
  4. Branch A: Macro shock identification (SVAR / narrative / external instruments)
  5. Branch B: Structural monetary / banking model identification
  6. Branch C: Micro-banking causal design (bank / loan / firm panel)
  7. Referee pushback mapped to the identification fix
  8. Matching identification to the JMCB policy use
  9. Execution bridge (StatsPAI / Stata MCP)
  10. Checklist
  11. Anti-patterns
  12. A note on local projections vs. VARs
  13. Worked vignette (illustrative)
  14. State what you do NOT identify
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jmcb-identification skill do?

Use when the identification argument is the bottleneck for a Journal of Money, Credit and Banking (JMCB) manuscript — macro shock identification (SVAR, narrative, sign/high-frequency monetary surprises), parameter identification in a monetary/banking model, or a micro-banking causal design. Stress-tests the data-to-object mapping to the JMCB bar before exhibits are finalized.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmcb-identification --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going