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 Empirical Design

ASecurity

Use when settling the measurement and estimation choices of a Journal of Financial Economics (JFE) manuscript — factor construction, portfolio sorts, Fama-MacBeth/GMM, standard-error clustering, and multiple-testing discipline. Covers the design/estimator layer; for causal identification of corporate-finance effects use jfe-identification.

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

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jfe Empirical Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jfe-empirical-design
description: Use when settling the measurement and estimation choices of a Journal of Financial Economics (JFE) manuscript — factor construction, portfolio sorts, Fama-MacBeth/GMM, standard-error clustering, and multiple-testing discipline. Covers the design/estimator layer; for causal identification of corporate-finance effects use jfe-identification.
---

# Empirical Design & Inference (jfe-empirical-design)

## When to trigger

- You sort on a characteristic but have not justified the variable, the breakpoints, or weighting
- You are choosing between Fama–MacBeth, panel regression, and GMM and unsure how to report
- Your standard errors are unclustered, or clustered on one dimension when two are needed
- You have an asset-pricing predictor but no out-of-sample or multiple-testing treatment
- Variable definitions are ad hoc and would not replicate

## The JFE design bar

JFE is known for nuts-and-bolts methodological rigor. Referees scrutinize measurement, estimator choice, standard errors, and inference discipline line by line. The goal is a design that a skeptical expert cannot dismantle on technical grounds. This is the journal that published **Fama & French (1993), "Common risk factors in the returns on stocks and bonds"** (the three-factor model), **Fama & French (2015), "A five-factor asset pricing model,"** and **Banz (1981), the size effect** — so an asset-pricing referee benchmarks your construction against that lineage directly. The best capital-markets paper each year wins JFE's **Fama-DFA Prize**; write to that standard. Code and non-proprietary data are mandatory at acceptance (Mendeley Data; see jfe-submission), so build a reproducible pipeline from the start.

## Asset pricing

### Factor / portfolio construction
- Justify the sorting variable economically and define it precisely (data source, lag, winsorization).
- State breakpoints (e.g., NYSE breakpoints vs. all-stock) and value- vs. equal-weighting, and show the choice does not drive the result.
- Report turnover and whether the strategy survives plausible transaction costs.

### Cross-sectional inference
- **Fama–MacBeth:** report Newey–West / Shanken-corrected standard errors; state lags. (Note Fama-MacBeth itself originates in *JPE* 1973; the factor-model machinery it serves is JFE's home turf via Fama-French.)
- **GMM / SDF:** state moment conditions, weighting matrix, and over-identification (J-test).
- Report alphas against the **Fama-French** benchmarks — CAPM, FF3, FF5 — plus momentum/q-factor where relevant, and show your factor survives **spanning regressions** against them. A single-benchmark alpha will not satisfy a JFE asset-pricing referee.

### Inference discipline
- **Out-of-sample:** show the predictor holds out of sample or in a holdout period.
- **Multiple testing:** when the predictor is one of many candidates, adjust (e.g., FDR / Bonferroni / data-mining-aware thresholds) and say so. Ignoring this is a known JFE red flag.

## Corporate finance

- Define every variable with source, timing, and units; tabulate in a variable-definition table.
- Winsorize/trim consistently and state the rule; show results are not winsorization artifacts.
- Choose fixed effects deliberately (firm, industry-by-year, etc.) and justify what each absorbs.
- **Standard errors:** cluster at the level of correlation in the residuals (often firm and/or time); use two-way clustering when both matter; match the cluster level to treatment assignment for causal designs.
- Report economic magnitudes, not just significance — a coefficient is a number with units.

## Checklist

- [ ] Every variable is defined with source, lag, and transformation
- [ ] Winsorization/trimming rule stated and shown not to drive results
- [ ] Sorting/breakpoint/weighting choices justified and stress-tested
- [ ] Estimator matches the question (FM / GMM / panel FE) and is reported correctly
- [ ] Standard errors clustered/corrected appropriately (often two-way)
- [ ] Alphas reported against multiple benchmark models
- [ ] Out-of-sample and multiple-testing discipline applied for predictors
- [ ] Economic magnitudes interpreted, not just t-stats

## Anti-patterns

- A new factor reported only in-sample, with no multiple-testing acknowledgment
- Standard errors that ignore cross-sectional or time-series correlation
- Breakpoints/weighting cherry-picked to maximize the spread
- Fama–MacBeth without Newey–West or Shanken corrections
- Variable definitions too vague to replicate
- Reporting t-statistics while never stating the economic size of the effect

## Output format

```
【Field】asset pricing | corporate finance
【Estimator】FM / GMM / panel FE / portfolio sort
【SE treatment】cluster dims / NW lags / Shanken
【Benchmarks】[models alphas are measured against]
【Inference discipline】out-of-sample? multiple-testing adjusted?
【Magnitudes stated】yes/no
【Next】jfe-robustness
```

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 →