Agent skill · Security

jebo-robustness

Use when a Journal of Economic Behavior & Organization (JEBO) result may be fragile to demand effects, multiple comparisons, specification, or tuning. Organizes robustness by the behavioral threat each check addresses — for experiments, observational designs, and simulations; it does not redesign the identification or write the prose.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jebo-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: 6 KB
Bundled scripts: none
Path: Journal-of-Economic-Behavior-and-Organization-Skills/skills/jebo-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 (jebo-robustness) ## When to trigger - An experiment has several treatment arms / outcomes and you have not corrected for multiplicity - A referee could attribute the effect to **experimenter demand**, confusion, or order effects - An observational result moves with controls, sample windows, or estimator choice - An agent-based result might be an artifact of grid, seed, or tuning choices - You have a long, unstructured "robustness" appendix and no map from check to threat ## Organize robustness by behavioral threat, not by appendix list At JEBO the right question is never "did we run enough checks?" but "for each way this could *not* be the behavioral mechanism, did we show it survives?" Build a threat → check map. The threats differ sharply across the four archetypes. ### Experiments (lab/online/field) | Threat | Check JEBO referees expect | |--------|----------------------------| | Experimenter demand | demand-treatment bounds (de Quidt-style), neutral framing, obfuscated objective | | Multiple comparisons | pre-registered primary outcome; MHT correction (Romano–Wolf, List–Shaikh–Xu, BH) across arms/outcomes | | Comprehension / confusion | results hold among

What's inside
Steps it walks through
  1. When to trigger
  2. Organize robustness by behavioral threat, not by appendix list
  3. Experiments (lab/online/field)
  4. Observational behavioral empirics
  5. Simulation / agent-based
  6. Distinguish "the effect is real" from "the mechanism is the claimed one"
  7. Execution bridge (StatsPAI / Stata MCP)
  8. Checklist
  9. Anti-patterns
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jebo-robustness skill do?

Use when a Journal of Economic Behavior & Organization (JEBO) result may be fragile to demand effects, multiple comparisons, specification, or tuning. Organizes robustness by the behavioral threat each check addresses — for experiments, observational designs, and simulations; it does not redesign the identification or write the prose.

How do I install it?

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