Individual skill
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.
Journal-of-Economic-Behavior-and-Organization-Skills/skills/jebo-robustness/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,760 bytes
Read excerpt
# 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.
