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

Jfi Identification Strategy

ASecurity

Use to audit the core analytical engine of a Journal of Financial Intermediation paper — for empirics, the causal design for a banking/credit question; for theory, the assumptions, equilibrium discipline, and proof exposition. It pressure-tests the design; it does not run the analysis.

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

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

Installs into .claude/skills of the current project.

Are you the author of Jfi Identification Strategy?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jfi-identification-strategy
description: Use to audit the core analytical engine of a Journal of Financial Intermediation paper — for empirics, the causal design for a banking/credit question; for theory, the assumptions, equilibrium discipline, and proof exposition. It pressure-tests the design; it does not run the analysis.
---

# Identification Strategy (jfi-identification-strategy)

## When to trigger

- Setting up or defending the empirical design of a banking/intermediation paper
- Setting up or defending the assumptions and propositions of a theory paper

## Empirical track (applied banking / credit)

JFI referees are unforgiving on identification in bank data. Build a credible **causal design** and defend
it:

- **Source of variation:** a regulatory change, supervisory shock, branching deregulation, a discontinuity
  in capital/eligibility rules, or a plausibly exogenous credit-supply shifter.
- **Modern estimators:** staggered DID with heterogeneity-robust estimators (Callaway–Sant'Anna,
  Sun–Abraham, de Chaisemartin–D'Haultfœuille), IV with weak-IV-robust inference, or RDD with the
  rdrobust toolkit.
- **Bank-data-specific threats:** bank selection into treatment, borrower–firm sorting, balance-sheet
  timing and mechanical reverse causality, and the **lending-channel separation** of credit supply from
  demand (firm×time fixed effects in matched lender–borrower panels).
- **Inference:** cluster at the level of treatment assignment (often bank or market); wild-cluster
  bootstrap when clusters are few.

## Theory track (intermediation models)

When the contribution is a **model**, identification means **analytical discipline**:

- State **assumptions** transparently and motivate each economically (what friction it encodes).
- Make **results** precise as propositions/lemmas; keep **proof exposition** readable — sketch the
  mechanism in the text, full proofs in an appendix.
- Argue **generality**: which results survive relaxed assumptions, and where the boundary lies.
- A **numerical example** (see jfi-data-analysis) can illustrate the mechanism without claiming empirical
  estimation.

## Anti-patterns

- OLS-plus-controls dressed up as identification on a bank panel
- Conflating credit supply and demand without firm×time absorption
- A theory whose key result silently depends on an unstated assumption
- Clustering at the wrong level, or ignoring few-cluster inference

## Output format

```
【Track】empirical / theory
【Design or assumptions】<the variation, or the key assumptions>
【Top threat / boundary】<the main objection + answer>
【Inference / generality】<clustering, or which results survive>
【Next skill】jfi-data-analysis
```

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 →