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

Jpube Identification Strategy

ASecurity

Use when the causal identification strategy is the bottleneck for a Journal of Public Economics (JPubE) manuscript — bunching at tax kinks/notches, regression kink (RKD), DID off reform rollout, IV from policy instruments, RDD at eligibility thresholds. Stress-tests the design against public-finance norms before tables are drafted.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jpube Identification Strategy?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jpube-identification-strategy
description: Use when the causal identification strategy is the bottleneck for a Journal of Public Economics (JPubE) manuscript — bunching at tax kinks/notches, regression kink (RKD), DID off reform rollout, IV from policy instruments, RDD at eligibility thresholds. Stress-tests the design against public-finance norms before tables are drafted.
---

# Identification Strategy (jpube-identification-strategy)

## When to trigger

- The empirical core is OLS + controls with an undefended causal claim
- A reform DID uses two-way fixed effects (TWFE) on staggered timing
- A bunching estimate lacks a defensible counterfactual density
- An IV's policy instrument has an unargued exclusion restriction
- You are unsure the design clears the JPubE public-finance bar

## The JPubE identification bar

JPubE rewards **credible identification of a policy-relevant parameter**, evaluated by public-finance specialists under single anonymized review (a minimum of two reviewers, with author identity known to them). Because the field's payoff is usually a behavioral elasticity feeding a welfare formula, the design must pin down the response to a tax, transfer, or program rule cleanly. The credibility ranking referees implicitly apply (strong → weaker):

1. **Bunching / notch designs** at a known kink or eligibility threshold, recovering an elasticity from excess mass
2. **RDD / RKD** at a sharp policy cutoff (eligibility, benefit schedule kink)
3. **DID / event study** off a credibly exogenous reform rollout, with modern estimators
4. **IV** with a policy instrument, strong first stage, and a defended exclusion restriction
5. **Selection-on-observables** — acceptable only as a complement, rarely as the spine

JPubE's comparative advantage is the **policy-induced discontinuity** — a tax kink, a benefit cliff, a reform date — so make the identifying variation an institutional feature a reader can see.

## Branch paths

### Branch A: Bunching at kinks / notches
- Estimate excess mass against a smooth counterfactual fit away from the kink; report the implied elasticity.
- Round-number / focal-point diagnostics; bin-width and excluded-region robustness.
- For notches, address the dominated region and optimization frictions; bound attenuation from frictions.

### Branch B: RDD / RKD
- McCrary / Cattaneo–Jansson–Ma density test for manipulation at the cutoff.
- Optimal bandwidth (Calonico–Cattaneo–Titiunik), bias-corrected CIs, bandwidth robustness.
- For RKD, identify off the slope change in the policy schedule; placebo kinks and covariate smoothness.

### Branch C: DID / event study off a reform
- Staggered adoption? Move beyond TWFE — Callaway–Sant'Anna, Sun–Abraham, or de Chaisemartin–D'Haultfœuille; report a Goodman-Bacon decomposition.
- Clean pre-trends via an event-study plot; cluster at the level of treatment (often state/jurisdiction).

### Branch D: IV from a policy instrument
- First-stage F strong; weak-IV-robust inference (Anderson–Rubin) where needed.
- Exclusion argued in three registers: theory, institutional detail, falsification.
- Report reduced form and OLS; state the LATE / compliers interpretation.

## Checklist

- [ ] Policy-induced identifying variation named in one sentence and defended as exogenous
- [ ] Design-appropriate diagnostics done (excess-mass fit / density / first-stage F / pre-trends)
- [ ] Modern estimator used where TWFE would be biased (staggered reform)
- [ ] Inference matched to assignment level (often jurisdiction); few-cluster handling
- [ ] Frictions / manipulation / placebo tests reported
- [ ] The recovered parameter maps to the welfare quantity the paper claims

## Anti-patterns

- Bunching with an arbitrary excluded region chosen to maximize the estimate
- TWFE on staggered reform timing with no heterogeneity-bias discussion
- IV that is "policy shock × lagged endogenous variable" with no exclusion argument
- An elasticity identified locally but sold as a global structural parameter

## Output format

```
【Design】bunching / RDD / RKD / DID / IV / other
【Identifying variation】one sentence (the policy discontinuity)
【Diagnostics done】[excess-mass fit, density, first-stage F, pre-trends, ...]
【Diagnostics missing】[...]
【Inference】clustering level + few-cluster handling
【Parameter → welfare】elasticity / sufficient stat mapped? [Y/N]
【Next step】jpube-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 →