identify
Design or review identification strategy for the sewage-house-prices project. Produces strategy memos with estimand, assumptions, pseudo-code, robustness plan, falsification tests, and referee objection anticipation. This skill should be used when asked to "design the strategy", "identify the effect", "write a strategy memo", or "think through identification".
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill identify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Identification Strategy Design or review an identification strategy for the sewage-house-prices project. **Input:** `$ARGUMENTS` — a research question, approach name (e.g. "hedonic", "dry spills"), or "review existing" to audit all current strategies. --- ## Project-Specific Context ### Existing Strategies 1. **Hedonic** — Cross-sectional: `log(price) ~ spill_metrics + controls | lsoa + year_qua
What does the identify skill do?
Design or review identification strategy for the sewage-house-prices project. Produces strategy memos with estimand, assumptions, pseudo-code, robustness plan, falsification tests, and referee objection anticipation. This skill should be used when asked to "design the strategy", "identify the effect", "write a strategy memo", or "think through identification".
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill identify --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/Auto-Empirical-Research-Skills, a repository with 3,244 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.