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

Rfs Identification

ASecurity

Use when the causal-inference or asset-pricing identification strategy is the bottleneck for a The Review of Financial Studies (RFS) manuscript — quasi-experiments (DID, IV, RDD, event study) and factor-model identification. Stress-tests the design before drafting tables.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Rfs Identification?

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

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

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

Download with Pro
Files
SKILL.md
---
name: rfs-identification
description: Use when the causal-inference or asset-pricing identification strategy is the bottleneck for a The Review of Financial Studies (RFS) manuscript — quasi-experiments (DID, IV, RDD, event study) and factor-model identification. Stress-tests the design before drafting tables.
---

# Identification Strategy (rfs-identification)

## When to trigger

- The empirical core is OLS + controls with an open endogeneity threat
- A DID uses two-way fixed effects (TWFE) without addressing staggered-adoption bias
- An IV has a weak first stage or a contestable exclusion restriction
- A cross-sectional asset-pricing claim rests on a factor that may be data-mined
- Reviewers will ask "what is your source of variation?" and you lack a crisp answer

## The RFS identification bar

RFS applies the **same high causal-inference standard as JF and JFE**: a claim of causality requires a credible source of exogenous variation, not a richer control set. RFS is more receptive than the others to *genuinely new questions* and to *structural / theoretical* identification — but novelty never substitutes for a clean design. Pick the strongest feasible strategy below.

**RFS-specific lever — Stage 1 design review.** Because RFS pioneered **Registered Reports** (pre-results review; Karolyi, "Kick-Starting the Review Process," RFS 27(2), 2014), an identification strategy can be **refereed before the results exist**. If you pursue this route, the design must be airtight on paper: pre-specified sample, treatment definition, estimator, diagnostics, and the exact tables to be produced — because that protocol becomes the binding commitment that earns *in-principle acceptance*. Even for a standard submission, draft the design as if it had to survive Stage 1 review with no results to fall back on.

### Design priority (corporate / household / empirical finance)

1. **Natural experiment / policy shock + DID** (incl. staggered and continuous treatment)
2. **Regression discontinuity** (a sharp institutional threshold: index inclusion, rating cutoff, covenant)
3. **Instrumental variables** (strong first stage + a defensible, finance-grounded exclusion)
4. **Event study** with clean windows and confound discussion
5. **Matching / propensity-score + DID** as a supplement, rarely as the sole strategy
6. **Structural estimation** when the question is about a parameter or counterfactual

### Branch A — DID
- Staggered adoption? → diagnose with Goodman-Bacon decomposition; estimate with Callaway–Sant'Anna, Sun–Abraham, or de Chaisemartin–D'Haultfœuille.
- Parallel trends: show an event-study plot with pre-trends, not a single pre-period dummy.
- Placebo: randomize treatment timing / units; report the placebo distribution.
- Continuous/dose treatment: justify the dose measure and its exogeneity.

### Branch B — IV
- First-stage F well above conventional weak-IV thresholds; if borderline, report Anderson–Rubin or other weak-IV-robust inference.
- Exclusion restriction defended in three registers: theory, institutional detail, and a placebo/falsification.
- Report the reduced form, not only the second stage.
- Address the instrument's own potential endogeneity explicitly.

### Branch C — RDD
- McCrary / density test for manipulation at the cutoff.
- Optimal bandwidth (Calonico–Cattaneo–Titiunik) plus at least three bandwidth-robustness checks.
- Covariate smoothness across the threshold.

### Branch D — Asset-pricing identification
- Factor construction: pre-register the sort/breakpoints logic; avoid look-ahead and survivorship bias.
- Standard errors: Fama–MacBeth or panel with errors clustered/adjusted appropriately (e.g., Newey–West, Driscoll–Kraay) — never naive OLS SEs on overlapping returns.
- Multiple testing: when the claim is a new predictor, confront the data-mining critique (see `rfs-robustness`).
- Out-of-sample and subsample stability for any predictability claim.

### Branch E — Structural / theory-driven
- State the identifying assumptions and which moments identify which parameters.
- Provide a counterfactual or decomposition that reduced form cannot deliver.
- Show the model fits untargeted moments.

## Checklist

- [ ] The source of exogenous variation is stated in one sentence
- [ ] Design-appropriate diagnostics run (parallel trends / density / first-stage F / SE choice)
- [ ] Placebo or falsification test included
- [ ] Standard-error structure matches the data (clustering / overlap / cross-section)
- [ ] Endogeneity threats are listed and each is addressed, not waved away
- [ ] For asset pricing, multiple-testing and out-of-sample concerns are anticipated
- [ ] Design is specified tightly enough to survive a Stage 1 (Registered Report) review with no results

## Anti-patterns

- TWFE on staggered treatment with no discussion of heterogeneous-effect bias.
- "We control for many observables, so the effect is causal."
- An IV that is "an exogenous event × a lagged endogenous variable."
- A new return predictor reported without confronting the multiple-testing critique.
- Naive standard errors on overlapping or autocorrelated returns.

## Output format

```
【Strategy】DID / RDD / IV / event study / asset-pricing / structural
【Source of variation】one sentence
【Diagnostics done】[parallel trends, density, first-stage F, SE choice, ...]
【Missing diagnostics】[...]
【SE structure】...
【Next step】rfs-empirical-design
```

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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', ...

686011 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 →