Agent skill

expecon-referee-strategy

Use when anticipating the experimentalist referee's objections for an Experimental Economics (ExpEcon) manuscript before submission. Pre-empts the standard pushbacks; it does not draft the response letter (see expecon-rebuttal).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill expecon-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: 9 KB
Bundled scripts: none
Path: Experimental-Economics-Skills/skills/expecon-referee-strategy/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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 (expecon-referee-strategy) ## When to trigger - The paper is analytically done and you want to pre-empt the objections an ExpEcon referee will raise - You suspect a specific weak point (a borderline procedure, modest power, a confound) and want to disarm it before submission - You need to decide what to add now vs. defend in the letter later - You want to read the draft the way two editors and two anonymous referees will ## Who reviews you here, and what they look for Experimental Economics uses **anonymous (double-blind) refereeing**, and accepted papers need the approval of **two editors** (检索于 2026-06;以官网为准). Your referees are practicing experimentalists. They are unimpressed by topical novelty and intensely focused on **design integrity**. They read in a predictable order: gates first, then the contrast, then inference, then reproducibility. Pre-empt each. ## The standard pushbacks, ranked by lethality 1. **"This is deception / the incentives aren't real."** Lethal and binary. If any procedure could be read as deceptive, name it explicitly and explain why it is *not* deception under the ESA definition (withholding ≠ misstating). Confirm every elicitation is i

What's inside
Steps it walks through
  1. When to trigger
  2. Who reviews you here, and what they look for
  3. The standard pushbacks, ranked by lethality
  4. Turning anticipated objections into pre-emptive moves
  5. A pre-submission self-review pass
  6. The demand-effect and experimenter-effect family
  7. Worked vignette (illustrative)
  8. Shaping the cover letter and reviewer pool
  9. Checklist
  10. Anti-patterns
  11. What the desk editor screens before referees ever see it
  12. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the expecon-referee-strategy skill do?

Use when anticipating the experimentalist referee's objections for an Experimental Economics (ExpEcon) manuscript before submission. Pre-empts the standard pushbacks; it does not draft the response letter (see expecon-rebuttal).

How do I install it?

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

Keep going