jpe-identification
Use when the empirical identification strategy is the bottleneck for a Journal of Political Economy (JPE) manuscript — quasi-experimental designs (DID, IV, RDD, event study) or structural estimation. Stress-tests the design and its economic interpretation before drafting tables; it does not write the model from scratch (see jpe-theory-model).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpe-identification --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Identification & Economic Interpretation (jpe-identification) ## When to trigger - The empirical core is OLS + controls with no defended causal claim - Staggered DID estimated with TWFE without addressing heterogeneity-bias critiques - IV with a weak first stage or a thin exclusion argument - Structural estimation where the source of parameter identification is not spelled out - A clean causal effect exists but its *economic* interpretation is not pinned down ## The JPE bar: credible identification AND economic meaning JPE accepts both reduced-form and structural work, but the bar has two parts that must *both* clear: 1. **Credible identification** — the estimate isolates the causal/structural object you claim. 2. **Economic interpretation** — the estimate maps onto a parameter or margin that economic theory cares about. A credibly identified effect with no economic meaning is a half-paper here. Reduced-form work should connect to a model or mechanism (see `jpe-theory-model`); structural work must make its identification transparent. Atheoretical correlation mining is the classic JPE desk-reject signal — and at JPE the desk screen is a co-editor (Chicago-centered board led by Est
- When to trigger
- The JPE bar: credible identification AND economic meaning
- Design priority (strong → acceptable)
- Branch paths
- Branch A — DID / event study
- Branch B — IV
- Branch C — RDD
- Branch D — Structural estimation
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Output format
What does the jpe-identification skill do?
Use when the empirical identification strategy is the bottleneck for a Journal of Political Economy (JPE) manuscript — quasi-experimental designs (DID, IV, RDD, event study) or structural estimation. Stress-tests the design and its economic interpretation before drafting tables; it does not write the model from scratch (see jpe-theory-model).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpe-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.