jle-robustness
Use when a The Journal of Law and Economics (JLE) manuscript's headline estimate must be shown to survive specification, sample, jurisdiction, and inference choices before submission or in an R&R. Builds the robustness suite a law-and-economics referee expects; it does not establish the primary identification (jle-identification) or format the exhibits (jle-tables-figures).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jle-robustness --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.
# Robustness Suite (jle-robustness) ## When to trigger - The main estimate of a legal/regulatory effect is in hand and you must show it is not an artifact of one specification - A referee asks "is this robust to alternative controls / sample / which jurisdictions / how you date the rule?" - The result depends on a bandwidth, a clustering choice, a treatment date, or a sample of included jurisdictions that could be questioned - You suspect specification-search concerns and want to pre-empt them ## The JLE robustness bar JLE referees — economists who know the institution — probe whether the estimated effect of the rule is **stable, honestly inferred, and not the product of researcher degrees of freedom**, with special attention to **legal-design choices**: how you dated the rule, which jurisdictions you treated as controls, whether enforcement was uniform. Robustness here is not a wall of regressions; it is a **targeted set of checks each tied to a specific threat to the legal identification**. Map every plausible objection to the one check that answers it, and show the point estimate barely moves. | Threat to the result | The check that answers it | |----------------------|---------
- When to trigger
- The JLE robustness bar
- Robustness craft
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Separating identification robustness from policy interpretation
- Anti-patterns
- Worked vignette (illustrative)
- The few-clusters problem is the JLE default, not the exception
- Referee pushback mapped to the robustness fix
- Output format
What does the jle-robustness skill do?
Use when a The Journal of Law and Economics (JLE) manuscript's headline estimate must be shown to survive specification, sample, jurisdiction, and inference choices before submission or in an R&R. Builds the robustness suite a law-and-economics referee expects; it does not establish the primary identification (jle-identification) or format the exhibits (jle-tables-figures).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jle-robustness --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.