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 Identification

ASecurity

Use when the causal identification or inference design is the bottleneck for a Journal of Financial Economics (JFE) manuscript — natural experiments, IV, staggered DID, RDD, and explicit endogeneity/selection treatment. Stress-tests the design before drafting tables; it does not finalize factor construction or estimators (see jfe-empirical-design).

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-identification --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jfe Identification?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jfe-identification
description: Use when the causal identification or inference design is the bottleneck for a Journal of Financial Economics (JFE) manuscript — natural experiments, IV, staggered DID, RDD, and explicit endogeneity/selection treatment. Stress-tests the design before drafting tables; it does not finalize factor construction or estimators (see jfe-empirical-design).
---

# Identification & Endogeneity (jfe-identification)

## When to trigger

- The empirical core is OLS + controls with endogeneity hand-waved away
- A DID uses two-way fixed effects with staggered adoption and you have not addressed the heterogeneous-treatment-effects bias
- Your IV's exclusion restriction or relevance is undefended
- Selection into the sample or treatment is plausible and unaddressed
- A referee could say "your X is endogenous to your Y"

## The JFE identification bar

JFE referees expect endogeneity and selection to be treated explicitly, and they expect every plausible alternative explanation to be ruled out — not waved away. Corporate-finance papers are held to a credible-design standard; asset-pricing papers to a disciplined-inference standard (see `jfe-empirical-design`). This skill covers the corporate-finance causal side; the design/estimator side lives in `jfe-empirical-design`.

JFE corporate finance descends from **Jensen & Meckling (1976), "Theory of the firm: Managerial behavior, agency costs and ownership structure"** — the agency-cost foundation and the journal's single most-cited paper. Modern reviewing keeps that demand for an economic *mechanism* but layers on a hard requirement for credible identification: a correlation between a governance/financing variable and an outcome will not survive review unless the endogeneity is convincingly handled. The best corporate-finance paper each year wins the **Jensen Prize**.

## Design priority (strong -> weaker)

1. **Natural experiment / exogenous shock + DID** (regulatory change, plausibly random policy, court ruling)
2. **Regression discontinuity** (a sharp rule with a running variable: index inclusion, covenant threshold, vote share)
3. **Instrumental variables** (strong first stage + a genuinely defensible exclusion restriction)
4. **Matching / entropy balancing + DID** (to reduce, not eliminate, selection)
5. **Structural estimation** (when the question is about deep parameters or counterfactuals)
6. OLS + controls (acceptable only with a frank endogeneity discussion and as a complement, rarely as the headline)

## Branches

### Branch A — DID / natural experiment
- Is adoption **staggered**? If so, two-way FE is biased under heterogeneous effects — use a modern estimator (Callaway–Sant'Anna, Sun–Abraham, de Chaisemartin–D'Haultfœuille, or stacked regression) and report a Goodman-Bacon decomposition.
- Parallel trends: plot the event study; show pre-trends are flat.
- Treatment exogeneity: argue why the shock is unrelated to the outcome's trajectory; address anticipation.
- Placebos: randomize treatment timing/units; falsification on unaffected outcomes.

### Branch B — IV
- First-stage strength: report the first-stage F / effective F (Olea–Pflueger); if weak, use weak-IV-robust inference (Anderson–Rubin).
- Exclusion: defend in three registers — theory, institutional detail, and a falsification/placebo.
- Report the reduced form and discuss the LATE/complier interpretation.
- Address whether the instrument itself could be endogenous.

### Branch C — RDD
- Manipulation test of the running variable (McCrary / `rddensity`).
- Optimal bandwidth (Calonico–Cattaneo–Titiunik) plus at least three bandwidth-sensitivity checks.
- Covariate continuity at the threshold; fuzzy-RDD first stage if applicable.

### Branch D — selection / sample construction
- State the population and every filter; show how filters could induce selection.
- Heckman / bounds / reweighting where selection is plausible — and say what each assumes.

### Branch E — structural
- Make the economic mechanism and identifying assumptions explicit.
- Provide a counterfactual and validate against reduced-form moments where possible.

## Checklist

- [ ] The identifying variation is named and its exogeneity argued, not assumed
- [ ] Staggered DID uses a heterogeneity-robust estimator + Bacon decomposition
- [ ] Parallel-trends / continuity / first-stage-strength evidence is shown
- [ ] Placebo and falsification tests are run
- [ ] Standard errors are clustered at the level of treatment assignment
- [ ] Every alternative explanation a referee would raise has a counter-test
- [ ] Anticipation / pre-treatment manipulation is addressed

## Anti-patterns

- Two-way FE on staggered adoption with no acknowledgment of the bias literature
- An IV that is "an exogenous event times a lagged endogenous variable" — referees ask why the lag is exogenous
- "We argue the shock is exogenous" with no supporting evidence
- RDD reported at one bandwidth with no sensitivity
- Clustering at the wrong level (e.g., firm when treatment is at the state level)
- Treating endogeneity as a robustness footnote rather than the design's spine

## Output format

```
【Design】natural experiment / RDD / IV / matching+DID / structural / OLS
【Identifying variation】...
【Tests done】[parallel trends, first-stage F, McCrary, placebo, ...]
【Tests missing】[...]
【Cluster level】...
【Alternatives ruled out】[...] | 【Still open】[...]
【Next】jfe-empirical-design
```

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 →