rje-identification-strategy
Use when the identification or estimation strategy is the bottleneck for a RAND Journal of Economics (RJE) industrial-organization manuscript — structural demand/supply, entry and dynamic games, auctions, or reduced-form designs off mergers and regulation. Stress-tests the design to the IO-flagship bar before tables are drafted.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rje-identification-strategy --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 (rje-identification-strategy) ## When to trigger - Your structural model's identification (instruments, functional form, moments) is unargued - A merger/regulation evaluation rests on TWFE over staggered timing with no modern estimator - An IV's first stage or exclusion restriction is weak in an IO setting - You are unsure your design clears the RJE industrial-organizatio
What does the rje-identification-strategy skill do?
Use when the identification or estimation strategy is the bottleneck for a RAND Journal of Economics (RJE) industrial-organization manuscript — structural demand/supply, entry and dynamic games, auctions, or reduced-form designs off mergers and regulation. Stress-tests the design to the IO-flagship bar before tables are drafted.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rje-identification-strategy --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.