Individual skill
jeea-robustness
Use when the headline result of a Journal of the European Economic Association (JEEA) manuscript needs to be shown stable to specification, sample, inference, and (for theory) assumption perturbations. Organizes robustness around the actual threats a general-interest referee will raise; it does not design the main result.
Journal-of-the-European-Economic-Association-Skills/skills/jeea-robustness/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- 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,411
- 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
- design 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 · 6,323 bytes
Read excerpt
# Robustness (jeea-robustness)
## When to trigger
- The main estimate moves when a referee imagines a different specification
- Inference rests on assumptions (homoskedasticity, few clusters) you have not stressed
- A theory result might hinge on one functional form or parameter range
- You have a pile of "robustness tables" but no organizing logic
## The JEEA robustness bar
A general-interest referee does not want a wall of extra columns — they want to know the **headline result survives the threats that matter**. Organize robustness by **threat to the claim**, not by "more specifications." Each robustness exhibit should answer a specific objection a JEEA referee would raise, and the headline magnitude should be **stable in sign and roughly in size** across the credible perturbations. Report everything as **standard errors / confidence sets, never significance asterisks**, and ensure every robustness check is reproducible for the **JEEA Data Editor** check.
## Robustness organized by threat