Agent skill · Workflow & Productivity

jpe-rebuttal

Use when a Journal of Political Economy (JPE) decision letter (R&R or reject-with-encouragement) has arrived and you need to draft the response-to-referees letter and revision plan. Structures the response and the diff; it does not redo the analysis (route back to jpe-identification / jpe-theory-model / jpe-robustness first).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpe-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: 5 KB
Bundled scripts: none
Path: Journal-of-Political-Economy-Skills/skills/jpe-rebuttal/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

# R&R Response & Rebuttal (jpe-rebuttal) ## When to trigger - A JPE R&R (or reject-with-encouragement-to-resubmit) letter has arrived - You have referee reports and need a point-by-point response plan - You are deciding which requests to implement, which to push back on, and how - The revision is drafted and you need the response letter to accompany it > Do the revisions *before* writing the letter. The letter documents changes already made; it should never promise work that is not in the revised manuscript. ## Reading the decision letter - The **co-editor's letter** is the binding document (at JPE the handling co-editor — Chicago-centered board led by Esteban Rossi-Hansberg, or a companion lead editor: John List for JPE Microeconomics, Greg Kaplan for JPE Macroeconomics — writes it). Identify which referee points the co-editor flags as essential vs. optional and prioritize accordingly. - Separate requests into: (a) must-do for the co-editor, (b) reasonable and cheap, (c) costly or wrong-headed. Negotiate (c) with evidence, not assertion. - A JPE co-editor and referees care most about the *economic argument*: expect demands to strengthen the mechanism, address a GE/selection object

What's inside
Steps it walks through
  1. When to trigger
  2. Reading the decision letter
  3. Response-letter structure
  4. Handling the JPE-typical demands
  5. Checklist
  6. Anti-patterns
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpe-rebuttal skill do?

Use when a Journal of Political Economy (JPE) decision letter (R&R or reject-with-encouragement) has arrived and you need to draft the response-to-referees letter and revision plan. Structures the response and the diff; it does not redo the analysis (route back to jpe-identification / jpe-theory-model / jpe-robustness first).

How do I install it?

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