Agent skill · Design & Presentation

ectheory-identification-strategy

Use when the assumptions, regularity conditions, and asymptotic results are the bottleneck for an Econometric Theory (ET) theorem-proof paper — adapt "identification" to mean stating defensible assumptions, proving the limit theory, and establishing generality, not causal design.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ectheory-identification-strategy --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Econometric-Theory-Skills/skills/ectheory-identification-strategy/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

# Assumptions, Results & Proof Plan (ectheory-identification-strategy) ## When to trigger - The estimator/test is stated but the **regularity conditions** under which it works are not pinned down - A proof has a gap, or an assumption is doing suspicious load-bearing work - You need to decide what limit theory applies (stationary vs nonstationary, fixed vs growing dimension) - You are unsure your result clears ET's rigor bar before drafting theorems ## The ET rigor bar (theory journal — adapt "identification" accordingly) At ET the analogue of an "identification strategy" is a **complete, defensible assumption set plus a correct, general proof**. The most common ET referee objection is an unstated or implausibly strong regularity condition. Treat the assumption-result-proof triple as the spine: 1. **Assumptions.** State each one explicitly and minimally. For every assumption ask: is it necessary, can it be weakened, and is it satisfied by a leading example DGP? Distinguish primitive conditions from high-level ones; if you use high-level conditions, show they hold in a concrete case. 2. **Results.** State theorems precisely — the object, the mode of convergence (in probability, in di

What's inside
Steps it walks through
  1. When to trigger
  2. The ET rigor bar (theory journal — adapt "identification" accordingly)
  3. Branch paths by environment
  4. Checklist
  5. Anti-patterns
  6. The assumption-audit table ET referees run first
  7. Worked vignette and the primitive-condition fixes
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ectheory-identification-strategy skill do?

Use when the assumptions, regularity conditions, and asymptotic results are the bottleneck for an Econometric Theory (ET) theorem-proof paper — adapt "identification" to mean stating defensible assumptions, proving the limit theory, and establishing generality, not causal design.

How do I install it?

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

Keep going