Individual skill

eer-robustness

Use when a European Economic Review (EER) result must be shown to survive specification, sample, measurement, and inference changes — the robustness battery referees demand. Builds the stress tests and organizes them; it does not establish the core identification or write the prose.

European-Economic-Review-Skills/skills/eer-robustness/SKILL.md

Read pinned source

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.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Robustness & Sensitivity (eer-robustness)

## When to trigger

- The headline estimate exists but its fragility has not been probed
- A referee (or co-author) suspects the result is driven by one sample/spec choice
- Inference assumptions (clustering, dependence, multiple testing) are unexamined
- A structural/quantitative result's sensitivity to parameters is not shown

## The EER robustness bar

A general-interest result must be **believable beyond the authors' favorite specification**. EER referees — methods-aware under single-anonymized review — expect a **disciplined battery**, not a scattershot appendix: vary the things that *could plausibly overturn the result*, report them transparently, and say which (if any) move the estimate. The goal is a result that is **robust where it matters and honest where it is fragile**. Robustness is not infinite specification mining; choose tests with a *reason*.

## The robustness battery (choose by design)
Back to top