Agent skill · Code Review & Quality

eer-referee-strategy

Use when anticipating the objections a European Economic Review (EER) referee will raise — under single-anonymized review across any field — and pre-empting them before submission. Maps likely pushback to fixes; it does not draft the response letter (use eer-rebuttal after a decision).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eer-referee-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: 5 KB
Bundled scripts: none
Path: European-Economic-Review-Skills/skills/eer-referee-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

# Referee Strategy (eer-referee-strategy) ## When to trigger - The paper is near-complete and you want to pre-empt predictable referee objections - You are unsure who the likely referees are and what they will attack - An editor desk-screen risk needs reducing (breadth/novelty/fit) - Before submission, to convert anticipated objections into in-paper defenses ## The EER referee reality EER review is **single-anonymized**: the referee sees who the authors are. The referee is typically an **expert in your exact design or field** and frequently **someone you cite**. Two gates precede them: an **editor desk-screen** (out-of-scope or low-novelty papers are rejected without review, and the **submission fee is non-refundable**), then **≥2 external referees** for an independent assessment (检索于 2026-06;以官网为准). The first decision is usually fast; the strategic move is to **pre-empt the predictable objections in the paper itself** so a referee has less to grab. ## Map objection → pre-emption | Likely objection | Pre-emption (where it lives) | |------------------|------------------------------| | "Not general interest / too narrow" | breadth hook on page one (`eer-topic-selection`, `eer-writing

What's inside
Steps it walks through
  1. When to trigger
  2. The EER referee reality
  3. Map objection → pre-emption
  4. Strategy moves
  5. Checklist
  6. Anti-patterns
  7. Worked vignette (illustrative)
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the eer-referee-strategy skill do?

Use when anticipating the objections a European Economic Review (EER) referee will raise — under single-anonymized review across any field — and pre-empting them before submission. Maps likely pushback to fixes; it does not draft the response letter (use eer-rebuttal after a decision).

How do I install it?

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