Agent skill · Code Review & Quality

rfs-identification

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.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rfs-identification --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Review-of-Financial-Studies-Skills/skills/rfs-identification/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 sam

What's inside
Steps it walks through
  1. When to trigger
  2. The RFS identification bar
  3. Design priority (corporate / household / empirical finance)
  4. Branch A — DID
  5. Branch B — IV
  6. Branch C — RDD
  7. Branch D — Asset-pricing identification
  8. Branch E — Structural / theory-driven
  9. Execution bridge (StatsPAI / Stata MCP)
  10. Checklist
  11. Anti-patterns
  12. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the rfs-identification skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rfs-identification --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.

Keep going