Agent skill

jhr-identification-strategy

Use when stress-testing causal identification for a Journal of Human Resources empirical-micro manuscript, including RCT, DID, RDD, IV, event studies, decompositions, policy shocks, and reconciliation with prior estimates.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhr-identification-strategy --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Journal-of-Human-Resources-Skills/skills/jhr-identification-strategy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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 (jhr-identification-strategy) ## When to trigger - The paper makes a causal claim - Referees could say selection, omitted variables, or policy timing drives the result - You need a reconciliation and sensitivity plan before submission ## Design checks - **RCT**: attrition, balance, compliance, spillovers, pre-analysis plan, multiple testing, cluster level. - **DID / event study**: timing, controls, pre-trends, treatment heterogeneity, anticipation, modern estimators where needed. - **RDD**: manipulation, bandwidth, polynomial order, covariate continuity, donut/alternative bandwidths. - **IV**: first stage, exclusion, monotonicity, weak-IV inference, LATE population. - **Decomposition/descriptive**: what is descriptive, what is causal, and what policy lesson follows. ## JHR-specific layer - Re-estimate or benchmark against close prior work when results differ. - Report sensitivity tests that explain which sample/specification choices matter. - Keep the public-policy interpretation tied to identified variation. ## Public-policy validity check For every causal claim, write the policy interpretation in LATE/ATT/descriptive terms: - **Who** is affected: treated

What's inside
Steps it walks through
  1. When to trigger
  2. Design checks
  3. JHR-specific layer
  4. Public-policy validity check
  5. Reviewer threat matrix
  6. What JHR referees probe first, by design
  7. Worked cutoff walkthrough
  8. Failure modes that end JHR reviews early
  9. Execution bridge (StatsPAI / Stata MCP)
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jhr-identification-strategy skill do?

Use when stress-testing causal identification for a Journal of Human Resources empirical-micro manuscript, including RCT, DID, RDD, IV, event studies, decompositions, policy shocks, and reconciliation with prior estimates.

How do I install it?

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