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

Smj Data Analysis

ASecurity

Use when estimating models and defeating endogeneity for a Strategic Management Journal (SMJ) manuscript — the single highest bar at SMJ. Executes and stress-tests the identification design from smj-methods; it does not design the study or build exhibits.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill smj-data-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Smj Data Analysis?

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

Security grade badge for Smj Data Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-smj-data-analysis/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-smj-data-analysis)

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

Download with Pro
Files
SKILL.md
---
name: smj-data-analysis
description: Use when estimating models and defeating endogeneity for a Strategic Management Journal (SMJ) manuscript — the single highest bar at SMJ. Executes and stress-tests the identification design from smj-methods; it does not design the study or build exhibits.
---

# Data Analysis & Endogeneity (smj-data-analysis)

## When to trigger

- You have a performance regression with no endogeneity / reverse-causality treatment
- DID, IV, matching, or a selection model is chosen but not yet stress-tested
- Reviewers will ask "how do you know this is causal and not selection?"
- You need to plan the mechanism test and the robustness battery

## The SMJ endogeneity mandate

Performance regressions with **unaddressed endogeneity or reverse causality are the #1 SMJ rejection reason.** Treat causal identification as a first-class part of the paper, not a footnote. The reviewer's mental model: *firms that make this strategic choice are different in ways that also affect performance.* You must close that door explicitly.

SMJ codifies this in Bettis, Gambardella, Helfat & Mitchell (2014), "Quantitative empirical analysis in strategic management," *SMJ* 35(7): 949–953: acknowledge endogeneity, make a good-faith effort to address it, and avoid **data snooping / p-hacking**. Report **economic magnitudes**, not just stars. SMJ will publish well-designed studies that report **null results** — so do not suppress a theory-relevant null.

## Threat → tool map

| Threat                                   | Primary tools                                              |
|------------------------------------------|------------------------------------------------------------|
| Self-selection into the strategic choice | IV, Heckman selection, PSM/CEM + DID, Rosenbaum bounds     |
| Reverse causality / simultaneity         | Exogenous shock + DID, lagged + Granger-style tests, IV    |
| Unobserved time-invariant heterogeneity  | Firm fixed effects (caveat: cannot fix time-varying confounds) |
| Omitted environmental confound           | Industry-year FE, region FE, controls, falsification tests |
| Measurement error in X                   | IV, multiple indicators, sensitivity analysis              |

Pick from the threat named in `smj-methods`; usually you will combine FE with one identification tool.

## Design-specific execution

### DID / natural experiment
- Test and **show** parallel pre-trends (event-study plot, not just a claim).
- If treatment timing is staggered, address heterogeneous-treatment-effect bias (Goodman-Bacon decomposition; Callaway–Sant'Anna or Sun–Abraham estimators) rather than naive two-way FE.
- Run placebo tests (fake treatment dates; unaffected units) and report effect dynamics.

### Instrumental variables
- Report the first-stage F (weak-instrument concern below conventional thresholds → use weak-IV-robust inference).
- Make the **exclusion** argument in prose: why the instrument affects performance *only* through the strategic choice. Reviewers reject IVs whose exclusion is implausible.
- Report the reduced form and over-identification tests where applicable.

### Matching (PSM / CEM) + DID
- Report covariate balance before/after; show common support.
- Matching handles selection on *observables only*; combine with DID and acknowledge residual selection on unobservables (bounds).

### Heckman selection
- Justify the exclusion restriction in the selection equation (a variable affecting selection but not the outcome). A Heckman with no valid exclusion restriction is identified only off functional form — reviewers know this.

## Mechanism & robustness

- **Mechanism test:** if you theorized a mediator, test it (prefer evidence beyond a Baron–Kenny mediation regression — e.g., moderation-of-process, subsample variation in the mechanism).
- **Magnitude, not just stars:** interpret the key effect in economic terms (e.g., "a 1 SD increase in X → a Y% change in performance"); SMJ cares about meaningful effects.
- **Robustness battery (report, do not bury):** alternative DVs; alternative samples (drop dominant industries/years); alternative estimators; clustering choices; prior performance; survivorship. Where feasible, show sensitivity to the identifying assumption (partial-identification / bounding).
- **Inference:** cluster standard errors at the level of treatment assignment (often firm); justify the choice.

## Checklist

- [ ] The identifying threat is stated and the matching tool is deployed
- [ ] Reverse causality is addressed by design, not by lags alone
- [ ] Firm (and industry-year) fixed effects included where appropriate
- [ ] DID: parallel-trends evidence shown; staggered-timing bias addressed; placebos run
- [ ] IV: first-stage strength reported; exclusion argued in prose; reduced form shown
- [ ] Matching: balance + common support reported; unobservable selection acknowledged
- [ ] Heckman: valid exclusion restriction, not functional-form identification
- [ ] Mechanism tested, not just asserted
- [ ] Robustness across DV, sample, estimator, and clustering reported
- [ ] Standard errors clustered at the assignment level

## Anti-patterns

- Cross-sectional correlations interpreted causally — an instant credibility loss at SMJ
- "We include fixed effects" treated as a complete endogeneity defense (FE miss time-varying confounds)
- IV with an exclusion restriction no reviewer would believe
- Heckman or PSM run mechanically with no defensible exclusion / balance
- Ignoring that firms self-select into the very strategic choice being studied
- Staggered DID with naive two-way FE and no heterogeneity correction
- A wall of robustness tables that never confronts the central threat
- Specification hunting until p < 0.05 (data snooping); reporting stars with no economic magnitude; suppressing a theory-relevant null — all discouraged by SMJ

## Output format

```
【Identifying threat】selection | reverse causality | unobserved heterogeneity | omitted confound
【Estimator】FE + [IV | DID | matching | Heckman | ...]
【Identification evidence】[parallel trends / first-stage F / balance / exclusion argument]
【Placebo / falsification】[done?]
【Mechanism test】[what + result]
【Robustness】[DV alt, sample alt, estimator alt, clustering]
【Residual threat acknowledged】...
【Economic magnitude reported】yes / add
【Nulls reported honestly (no p-hacking)】yes
【Next step】smj-contribution-framing
```

## Templates & resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — Stata/R/Python packages (reghdfe, ivreghdfe, csdid/did, psmatch2, rdrobust) and strategy data sources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SMJ p-hacking / null-results / endogeneity policy and the Bettis et al. (2014) editorial

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 →