Agent skill

expecon-rebuttal

Use when responding to a revise-and-resubmit or referee report for an Experimental Economics (ExpEcon) manuscript — including when a referee demands a new treatment, more sessions, or raises a deception/power concern. Plans the response; it does not run the new analysis.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill expecon-rebuttal --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: Experimental-Economics-Skills/skills/expecon-rebuttal/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

# Rebuttal Strategy (expecon-rebuttal) ## When to trigger - An R&R or rejection arrived and you must decide what to concede, contest, or re-run - A referee asks for a **new treatment or more sessions** — the costliest and most common ExpEcon request - A reviewer raised a **deception** or **power/inference-unit** concern that could be decisive - Two referees disagree, or the two editors' priorities differ, and you need a coherent plan ## The ExpEcon revision reality: new data is on the table Unlike journals where revisions are textual, an ExpEcon R&R often requires **collecting new data** — an added control treatment, more matching groups for power, or a robustness condition. Plan the response around that fact. 1. **Triage every comment** into: (a) **new data needed** (new treatment / more sessions), (b) **re-analysis** (correct inference unit, MHT correction, new test), (c) **clarification** (already in the paper, surface it), (d) **respectful disagreement** (with evidence). Most letters are mostly (b)–(c); isolate the (a) items because they set the timeline and budget. 2. **Address the gate concerns first and decisively.** A deception worry is existential: either prove the procedu

What's inside
Steps it walks through
  1. When to trigger
  2. The ExpEcon revision reality: new data is on the table
  3. Triaging the common ExpEcon requests
  4. Writing the response letter
  5. Worked vignette (illustrative)
  6. Budgeting the new-data round
  7. Checklist
  8. Keeping pre-registration credible through revision
  9. Anti-patterns
  10. When the decision is reject, not R&R
  11. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the expecon-rebuttal skill do?

Use when responding to a revise-and-resubmit or referee report for an Experimental Economics (ExpEcon) manuscript — including when a referee demands a new treatment, more sessions, or raises a deception/power concern. Plans the response; it does not run the new analysis.

How do I install it?

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