Agent skill · Security

jhe-robustness

Use when a Journal of Health Economics (JHE) result must be shown stable to specification, sample, inference, and mechanism threats before submission or in response to referees. Organizes robustness by identifying threat; it does not establish the design (jhe-identification) or build exhibits.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jhe-robustness --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: Journal-of-Health-Economics-Skills/skills/jhe-robustness/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

# Robustness Strategy (jhe-robustness) ## When to trigger - The headline estimate may be sensitive to specification, sample window, or functional form - Inference is suspect: few clusters (states), serial correlation, or multiple outcomes/subgroups - A referee will ask whether the result is a coverage/take-up artifact rather than the claimed effect - The mechanism story is asserted but not separated from competing explanations ## Robustness the JHE way: organize by threat, not by appendix A wall of starred alternative specifications persuades no one. JHE referees want each robustness check **mapped to a specific threat to the health-economics claim**, with the point estimate's *stability* — not its significance — as the object. Build the robustness section as a threat-response ledger: name the threat a health economist would raise, run the check that addresses it, and report whether the magnitude moves. The threats that recur at JHE are selection, concurrent policy, measurement of health/utilization, and inference with few policy clusters. ## Threat-to-check ledger | Threat to the claim | Check that addresses it | |---------------------|-------------------------| | Residual selecti

What's inside
Steps it walks through
  1. When to trigger
  2. Robustness the JHE way: organize by threat, not by appendix
  3. Threat-to-check ledger
  4. Sequencing
  5. Execution bridge (StatsPAI / Stata MCP)
  6. Checklist
  7. Anti-patterns
  8. The skewed-spending decision, made explicitly
  9. Worked vignette (illustrative)
  10. Output format
  11. Handoff boundary
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jhe-robustness skill do?

Use when a Journal of Health Economics (JHE) result must be shown stable to specification, sample, inference, and mechanism threats before submission or in response to referees. Organizes robustness by identifying threat; it does not establish the design (jhe-identification) or build exhibits.

How do I install it?

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