ecopol-identification
Use when the identification argument is the bottleneck for an Economic Policy (EP) manuscript — causal identification of a policy effect, or parameter identification in a quantitative policy model. Stress-tests it to the EP bar (credible to an academic discussant, legible to a policy discussant) before exhibits are finalized.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-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 Strategy (ecopol-identification) ## When to trigger - A policy effect rests on OLS + controls, or TWFE on staggered policy rollout - An IV's exclusion restriction is institutional hand-waving, not an argument - A structural/quantitative policy model is estimated but it is unclear *what in the data* pins each parameter - The counterfactual policy scenario relies on parameters whose policy-invariance is undefended - You must convince **two discussants at once** — one who will probe the econometrics, one who needs the design to be legible enough to trust the policy number ## The EP identification bar EP papers are debated by two named discussants and read by policymakers, so identification must be **both rigorous and legible**. The academic discussant will apply the modern frontier; the policy discussant must be able to follow *why* the estimate is causal without reading the appendix. The discipline: make the **mapping from data/variation to the policy claim** explicit in the main text in plain language, and carry the formal defense in a technical appendix (EP's house split — accessible main text, rigorous appendix). Because results feed a policy recommendation, the m
- When to trigger
- The EP identification bar
- Branch A: Empirical causal design (most EP papers)
- Branch B: Structural / quantitative policy model
- Translate the design for the policy reader
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Output format
What does the ecopol-identification skill do?
Use when the identification argument is the bottleneck for an Economic Policy (EP) manuscript — causal identification of a policy effect, or parameter identification in a quantitative policy model. Stress-tests it to the EP bar (credible to an academic discussant, legible to a policy discussant) before exhibits are finalized.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecopol-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.