ecta-referee-strategy
Use to red-team an Econometrica manuscript before submission and to anticipate co-editor and referee objections — proof gaps, generality, missing finite-sample evidence, and competing methods. Predicts and pre-empts attacks; it does not draft the response letter after reports arrive (use ecta-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecta-referee-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.
# Referee and Co-Editor Strategy (ecta-referee-strategy) ## When to trigger - Before submitting, to find the hole a referee will find first - When you suspect a proof step or a generality claim is the weak point - When choosing how to present the contribution to survive a demanding referee pool - When deciding what to put in the body vs. the Supplemental Material to pre-empt objections Econometrica's referees are usually experts in exactly your method — often the authors of the results you build on. Reviews are demanding, multi-round, and the **co-editor and referees check proofs closely**. Assume every step will be read by someone who could have proven it themselves. ## How Econometrica review works - A submission is screened for eligibility (ES membership of at least one author, fee, the **45-page** limit) and routed by the **Editor** (Marina Halac, Yale, 2025–2029 — verify) to a handling **Co-Editor** from a small board (e.g., Keisuke Hirano, Aureo de Paula, Marciano Siniscalchi, Pete Klenow, Patrick Kline). The Co-Editor's read carries decisive weight and they often pick referees who *are* the authors of the results you extend. - Referees verify proofs, not just plausibility. A
- When to trigger
- How Econometrica review works
- Red-team the paper
- Presentation choices that help
- Suggested vs. excluded referees
- Checklist
- Anti-patterns
- Output format
What does the ecta-referee-strategy skill do?
Use to red-team an Econometrica manuscript before submission and to anticipate co-editor and referee objections — proof gaps, generality, missing finite-sample evidence, and competing methods. Predicts and pre-empts attacks; it does not draft the response letter after reports arrive (use ecta-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecta-referee-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 984 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.