Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jfe Robustness

ASecurity

Use when a Journal of Financial Economics (JFE) result needs the exhaustive robustness battery the journal is known for — alternative measures, subsamples, specifications, and falsification. Builds the stress-test plan; it does not choose the core estimator (jfe-empirical-design) or the identification design (jfe-identification).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jfe-robustness --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jfe Robustness?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jfe Robustness
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jfe-robustness/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jfe-robustness)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jfe-robustness
description: Use when a Journal of Financial Economics (JFE) result needs the exhaustive robustness battery the journal is known for — alternative measures, subsamples, specifications, and falsification. Builds the stress-test plan; it does not choose the core estimator (jfe-empirical-design) or the identification design (jfe-identification).
---

# Robustness Battery (jfe-robustness)

## When to trigger

- The result holds in the baseline but you have not tried obvious alternatives
- A referee could ask "does this survive a different measure / sample / specification?"
- You are unsure which robustness tests belong in the main text vs. the Internet Appendix
- You suspect a result might be fragile and want to find out before a referee does

## Why robustness is JFE's signature

JFE's referee culture rewards thoroughness: a result is credible only after it survives a wide battery of sensible alternatives, and reviewers expect *every* alternative explanation to be addressed, not merely the convenient ones. A fragile result that breaks under a routine variation is a classic JFE rejection. The headline tests live in the main text; the rest go to the Internet Appendix, which JFE asks you to append to the end of the main manuscript file (see `jfe-internet-appendix`).

Because JFE mandates a **code + non-proprietary-data deposit** (Mendeley Data) at acceptance for post-2021 submissions, your robustness battery must be *runnable*, not just described — referees increasingly probe reproducibility after the field-wide concerns about non-replicable factors (the Fama-French factor lineage is the benchmark) and fragile staggered-DID results.

## The robustness dimensions

Work through each; for each, decide main-text vs. appendix.

### 1. Alternative measures
- Re-measure the dependent and key independent variables (different proxies, data sources, definitions).
- Show the result is not an artifact of one operationalization.

### 2. Alternative specifications
- Add/remove fixed effects; vary the control set; show coefficient stability (a coefficient-stability / Oster bounds argument for omitted-variable bias where relevant).
- Functional form: levels vs. logs, linear vs. nonparametric.

### 3. Alternative samples
- Drop influential years (e.g., the financial crisis), industries, or large firms.
- Subperiod stability; exclude the most/least-treated units.

### 4. Alternative inference
- Re-cluster at a different level; wild-cluster bootstrap when clusters are few.
- Permutation/randomization inference where appropriate.

### 5. Falsification & placebos
- Outcomes that should *not* respond if your story is right.
- Placebo timing or placebo treatment groups.

### 6. Ruling out alternative explanations
- For each rival story a referee could tell, design a test that distinguishes it from yours.
- This is the single most important block for JFE — list the alternatives explicitly and kill them one by one.

## Checklist

- [ ] Key variables re-measured with at least one alternative proxy
- [ ] Specification varied (FE set, controls, functional form) with stable coefficients
- [ ] Subsample / subperiod stability shown; crisis or outlier periods isolated
- [ ] Inference re-done at an alternative cluster level (or wild bootstrap)
- [ ] Falsification / placebo tests run and reported
- [ ] Each named alternative explanation has a distinguishing test
- [ ] Main-text vs. Internet-Appendix split decided for every test

## Anti-patterns

- Reporting only the robustness checks that pass ("cherry-picked specifications")
- A "robustness" section that re-runs the same model with one extra control and calls it done
- Leaving an obvious rival explanation untested and hoping no referee notices
- A result that flips sign or loses significance under a routine variation, reported without comment
- Dumping every check into the main text so the paper becomes unreadable

## Output format

```
【Headline result】...
【Robustness done】measures[...] specs[...] samples[...] inference[...] placebos[...]
【Alternatives ruled out】[story -> test] pairs
【Fragile under】[...] (if any — fix before submission)
【Main-text vs. appendix】split decided: yes/no
【Next】jfe-tables-figures
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →