Agent skill · Testing & QA

jbes-identification-strategy

Use when the methodological core of a Journal of Business & Economic Statistics (JBES) paper is the bottleneck — assumptions, regularity conditions, asymptotic theory, and Monte Carlo design for a new estimator, test, or algorithm. Stress-tests the method's validity, not a causal design.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbes-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: 7 KB
Bundled scripts: none
Path: Journal-of-Business-and-Economic-Statistics-Skills/skills/jbes-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

# Method Validity & Asymptotics (jbes-identification-strategy) ## When to trigger - The estimator/test is proposed but its assumptions and limiting theory are not nailed down - The asymptotic distribution, consistency, or rate is asserted without full conditions - The Monte Carlo design does not yet show where the method holds and where it breaks - For an applied paper, what parameter your method identifies (and under what conditions) is unclear ## What "identification" means at a methods journal At JBES the load-bearing question is usually not a causal-design story but **whether the method delivers valid inference for its target under stated conditions**. Because JBES demands methodological novelty with **clear empirical relevance**, the assumptions cannot be so strong that no real data set — including the paper's own application — satisfies them. The credibility ladder a referee applies, strongest first: 1. **Identification of the target** — the parameter/functional is identified from the population moments the method uses, under stated conditions. 2. **Regularity conditions** — explicit (moment existence, smoothness, mixing/dependence, rate and rank conditions), each motivated a

What's inside
Steps it walks through
  1. When to trigger
  2. What "identification" means at a methods journal
  3. Branch paths
  4. Execution bridge (StatsPAI / Stata MCP)
  5. Checklist
  6. Anti-patterns
  7. Worked vignette: nailing down a weak-IV-robust estimator's validity
  8. Referee-pushback patterns on method validity (venue-specific fixes)
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jbes-identification-strategy skill do?

Use when the methodological core of a Journal of Business & Economic Statistics (JBES) paper is the bottleneck — assumptions, regularity conditions, asymptotic theory, and Monte Carlo design for a new estimator, test, or algorithm. Stress-tests the method's validity, not a causal design.

How do I install it?

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