qje-identification
Use when the causal identification strategy is the bottleneck for a Quarterly Journal of Economics (QJE) manuscript — RCT, staggered DID, IV, RDD, event study. Stress-tests the design to the QJE general-interest bar before tables are drafted.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill qje-identification --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.
# Causal Identification (qje-identification) ## When to trigger - The empirical core is OLS + controls with an undefended causal claim - A DID uses two-way fixed effects (TWFE) on staggered timing without modern estimators - An IV's first stage is weak or the exclusion restriction is unargued - An RDD lacks a McCrary density test or bandwidth-robustness - You are unsure your design clears the QJE
What does the qje-identification skill do?
Use when the causal identification strategy is the bottleneck for a Quarterly Journal of Economics (QJE) manuscript — RCT, staggered DID, IV, RDD, event study. Stress-tests the design to the QJE general-interest bar before tables are drafted.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill qje-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.