Agent skill · Testing & QA

acr-identification

Use when the empirical identification strategy is the bottleneck for a 《会计研究》 (Accounting Research) manuscript — exogenous standard / regulatory changes (event study, DID), PSM, Heckman, IV — and you need to stress-test the design before drafting tables. Prefers standard/regulatory shocks as the cleanest accounting identification source.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill acr-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: 3 KB
Bundled scripts: none
Path: Accounting-Research-Skills/skills/acr-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

# 因果识别策略(acr-identification) ## 触发时机 - 实证主体仅有 OLS + 控制变量,未处理内生性 - 用了准则/监管变更但没把它做成干净的 DID/事件研究 - DID 用 TWFE 但未回应近年异质性处理批评 - 自选择明显(如自愿披露、聘请大所)却没 PSM/Heckman ## 设计优先级(本刊偏好,强 → 弱) 1. **准则/监管外生变更 + DID 或事件研究**(本刊黄金来源:统一推行、对企业近似外生) 2. **断点回归**(清晰的监管门槛,如某规模/比例阈值触发披露义务) 3. **PSM + DID**(处理自选择 + 时间趋势) 4. **Heckman 两阶段**(自选择,如是否自愿披露、是否聘大所) 5. **工具变量**(强工具 + 排他性论证,会计场景工具较难,慎用) 6. OLS + 严密内生性讨论(描述性/计量基准类文章可接受) ## 分支路径 ### 分支 A:准则/监管变更 DID(首选) - 处理时点对齐准则**实际施行日**(见 `acr-institutional-standards`),非发布日 - 处理组/对照组界定来自适用范围(强制 vs 未覆盖) - 平行趋势:事件研究图必须画;分批施行优先用 Callaway-Sant'Anna / Sun-Abraham,回应异质性处理偏误 - 安慰剂:随机处理时点 / 随机处理组 500–1000 次 - 预期效应:是否存在抢先反应(提前调整会计政策) ### 分支 B:PSM / PSM+DID - 报告匹配变量、匹配方法(近邻/卡尺/核)、匹配后平衡性检验 - 共同支撑域、匹配前后差异 ### 分支 C:Heckman - 第一阶段选择方程须有**排他性约束变量**(影响选择不直接影响结果) - 报告逆米尔斯比率显著性与方向 ### 分支 D:RDD / IV - RDD:McCrary 操纵检验、最优带宽 + 带宽稳健性、协变量平滑 - IV:第一阶段 F ≥ 10,排他性需理论/制度/安慰剂三段论证 ## 执行桥(StatsPAI / Stata MCP) 把识别主张**跑出来并审计**,而不是只做论证。完整映射见 [`execution-with-mcp`](../../../shared-resources/empirical-methods/execution-with-mcp.md)。《会计研究》是档案式会计实证——准则/监管变更的 DID、IV 与盈余类设计居多,正合企业因果链。 1. `detect_design` → `recommend` → 用 `as_handle=true` 拟合 → `audit_result` 列出设计尚欠的检查。 2. **交错 DID:**`callaway_santanna` / `

What's inside
Steps it walks through
  1. 触发时机
  2. 设计优先级(本刊偏好,强 → 弱)
  3. 分支路径
  4. 分支 A:准则/监管变更 DID(首选)
  5. 分支 B:PSM / PSM+DID
  6. 分支 C:Heckman
  7. 分支 D:RDD / IV
  8. 执行桥(StatsPAI / Stata MCP)
  9. 必查清单
  10. 反模式
  11. 本刊识别策略的审稿期待(决策表)
  12. 微型走查:金融工具准则与减值计提(数字示意)
  13. 审稿人追问与本刊语境修法
  14. 校准锚点
More from Awesome-Journal-Skills
All skills →
About this skill
What does the acr-identification skill do?

Use when the empirical identification strategy is the bottleneck for a 《会计研究》 (Accounting Research) manuscript — exogenous standard / regulatory changes (event study, DID), PSM, Heckman, IV — and you need to stress-test the design before drafting tables. Prefers standard/regulatory shocks as the cleanest accounting identification source.

How do I install it?

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