STATA code pattern library for empirical archival accounting research. Provides tested syntax from 126 peer-reviewed JAR (Journal of Accounting Research) replication files (2017-2025). Use when the user asks procedural questions like "How do I implement [method]?" or "Show me code for [technique]" — including: entropy balancing, propensity score matching (PSM), difference-in-differences (DiD), regression discontinuity (RDD), instrumental variables (IV), event studies (CAR/BHAR), survival analysis, Fama-MacBeth regressions, bootstrap, quantile regression, reghdfe/xtreg/areg, clustering standard errors, fixed effects, esttab/outreg2 table formatting, winsorization, leads/lags. Users can specify their variables (e.g., treatment, outcomes, controls) and receive adapted syntax. NOTE: This skill provides code patterns from published papers, not research design advice.
Scope and Limitations This skill is a code pattern library , not a methodological advisor. | Can Do | Cannot Do | | | | | Show how published papers implemented methods | Explain when to use one method over another | | Provide tested STATA syntax | Advise on identification strategy | | Indicate which robustness tests accompany analyses | Discuss research design trade offs | | Cite source papers for code patterns | Recommend optimal research design | When users ask methodology questions (e.g.,…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/18-jusi-aalto-stata-accounting-research · pinned to the source commit
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git
cd Auto-Empirical-Research-Skills
git checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills/18-jusi-aalto-stata-accounting-research"
cp -r "skills/18-jusi-aalto-stata-accounting-research" ".claude/skills/18-jusi-aalto-stata-accounting-research"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 692e9fa3fea4. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.