jru-robustness
Use when a Journal of Risk and Uncertainty (JRU) result may be sensitive to specification, incentive frame, sample, or inference. Organizes robustness by the threat to the risk/uncertainty parameter; it does not invent evidence or citations.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-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 Strategy (jru-robustness) ## When to trigger - The headline risk/ambiguity parameter shifts under a different functional form (CRRA vs. CARA vs. expo-power) and you are unsure which to report - An experimental result might be an artifact of stakes, order, the random-incentive system, or a particular elicitation device - A referee will ask whether the finding survives EU vs. non-EU specifications, or pooled vs. heterogeneous-type estimation - Multiple hypotheses are tested across many lottery menus or treatments and no correction is in place ## Organize robustness by threat, not by appendix A JRU robustness section earns its place when every check is tied to a **specific threat to the parameter's interpretation**. List the threats first, then the check that answers each. | Threat to the result | The check that addresses it | |----------------------|-----------------------------| | Functional-form dependence of the risk parameter | Re-estimate under CRRA, CARA, expo-power; report whether the *qualitative* claim is stable | | Utility–weighting confound | Show the result holds under a model that separates u from w (e.g., RDU/CPT, not just EU) | | Elicitation-device artifac
- When to trigger
- Organize robustness by threat, not by appendix
- Sequencing
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Distinguish robustness from a specification search
- Robustness the experiment specifically demands
- Worked vignette (illustrative)
- Output format
What does the jru-robustness skill do?
Use when a Journal of Risk and Uncertainty (JRU) result may be sensitive to specification, incentive frame, sample, or inference. Organizes robustness by the threat to the risk/uncertainty parameter; it does not invent evidence or citations.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jru-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.