expecon-robustness
Use when an Experimental Economics (ExpEcon) result may be a power artifact, multiple-comparisons artifact, or sensitive to the inference unit, exclusions, or design choices. Hardens the statistical case; it does not design the experiment or draft prose.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill expecon-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 & Inference (expecon-robustness) ## When to trigger - A referee asks "is the study adequately powered?" and there is no sample-size justification - You ran several treatments / outcomes and report many p-values without correction - Inference treats individual decisions as independent when subjects interact in groups - Results move when you change the exclusion rule, the outcome measure, or pool/unpool sessions ## The ExpEcon inference stack Experimental control buys clean identification; it does not buy clean *inference*. Five things separate a robust ExpEcon paper from a fragile one. ### 1. Power / sample-size justification (do this before data, defend it after) - Pre-specify the **minimum detectable effect (MDE)** that is economically meaningful and the power to detect it, at the **correct unit** (session or matching group, not individual decision). A study powered on individual n but analyzed at the group level is overstated. - Use pilot or prior-literature variances; for interactive games, simulate at the group level. Report the realized power for the primary comparison, not just a post-hoc "we found p<0.05." - A clean, well-powered **null** is publishable here — e
- When to trigger
- The ExpEcon inference stack
- 1. Power / sample-size justification (do this before data, defend it after)
- 2. The unit-of-observation problem
- 3. Multiple treatments & multiple hypotheses
- 4. Non-parametric vs. parametric
- 5. Robustness to design and analysis choices
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Worked vignette (illustrative)
- Referee pushback mapped to the fix
- A minimal robustness panel to pre-build
- Output format
What does the expecon-robustness skill do?
Use when an Experimental Economics (ExpEcon) result may be a power artifact, multiple-comparisons artifact, or sensitive to the inference unit, exclusions, or design choices. Hardens the statistical case; it does not design the experiment or draft prose.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill expecon-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.