Agent skill · Data & Analytics

jhe-identification

Use when the identification argument is the bottleneck for a Journal of Health Economics (JHE) manuscript — quasi-experimental health-policy variation, selection into insurance/treatment, eligibility RD, or structural identification of demand/provider parameters. Stress-tests the data-to-estimand mapping to the JHE bar before exhibits are finalized; it does not write prose or build the package.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhe-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: 9 KB
Bundled scripts: none
Path: Journal-of-Health-Economics-Skills/skills/jhe-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 (jhe-identification) ## When to trigger - A causal health-policy claim rests on OLS + controls or TWFE on staggered state adoptions - An insurance/treatment effect is contaminated by selection that is not modeled - An eligibility cutoff (income, age-65 Medicare, kink in subsidy schedule) is used without an RD defense - A structural insurance-demand or provider-response parameter is estimated but it is unclear what identifies it - You are unsure the design clears JHE's credible-causal-plus-institutional bar ## The JHE identification bar JHE referees demand **credible causal identification *and* institutional realism**: the mapping from a source of variation to the health-economics estimand must be explicit, falsifiable, and consistent with how the program or market actually works. Two failure modes get punished hardest here: (1) ignoring **selection** — into insurance, into treatment, into the sample — that the health setting makes first-order; and (2) treating a **policy variation as exogenous** when institutional detail (phase-ins, waivers, simultaneous reforms, anticipation) says it is not. State the estimand, name the assumption, show the diagnostic tha

What's inside
Steps it walks through
  1. When to trigger
  2. The JHE identification bar
  3. Design paths
  4. Path A: Quasi-experimental health-policy variation (DiD / event study)
  5. Path B: Selection into insurance / treatment
  6. Path C: Eligibility RD / kink
  7. Path D: IV / structural identification
  8. Execution bridge (StatsPAI / Stata MCP)
  9. Checklist
  10. Anti-patterns
  11. Worked vignette (illustrative)
  12. Referee pushback mapped to the identification fix
  13. A note on health-specific identification traps
  14. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jhe-identification skill do?

Use when the identification argument is the bottleneck for a Journal of Health Economics (JHE) manuscript — quasi-experimental health-policy variation, selection into insurance/treatment, eligibility RD, or structural identification of demand/provider parameters. Stress-tests the data-to-estimand mapping to the JHE bar before exhibits are finalized; it does not write prose or build the package.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhe-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