Agent skill · Code Review & Quality

jpube-rebuttal

Use when a Journal of Public Economics (JPubE) decision letter arrives (revision or reject) and a response strategy, response letter, or appeal decision is needed. Structures the revision and response for single-anonymized specialist review; it does not redo the analysis (route to the relevant jpube-* skill).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpube-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: 6 KB
Bundled scripts: none
Path: Journal-of-Public-Economics-Skills/skills/jpube-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

# Rebuttal & Revision (jpube-rebuttal) ## When to trigger - A JPubE decision letter arrived: major/minor revision, or reject - You have specialist referee reports and need a response strategy - You are unsure how to prioritize conflicting public-finance referee demands - You are weighing whether to use the single permitted appeal ## JPubE reality JPubE uses **single anonymized review** with a minimum of two reviewers who **know your identity**, and the handling editor (under the Hendren–Kopczuk editorial leadership) synthesizes their reports through **Editorial Manager**. The **handling editor's letter is the contract**: it ranks which referee points are binding. Because referees are public-finance specialists, expect demands aimed at the *credibility of the policy parameter and its welfare mapping* — the counterfactual in a bunching design, the pre-trends in a reform DID, the sufficient-statistics assumptions, the external validity of a local elasticity. ## Triage protocol 1. **Decode the editor.** A point the editor underscores is binding; a single-referee point the editor passed over is lower priority (but still answer it). 2. **Classify every comment** as *fundamental* (needs n

What's inside
Steps it walks through
  1. When to trigger
  2. JPubE reality
  3. Triage protocol
  4. Response-letter structure
  5. Appeals (use sparingly)
  6. Checklist
  7. Anti-patterns
  8. Referee pushback → venue-specific fix
  9. Worked vignette: turning a fundamental into a settled point (illustrative)
  10. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpube-rebuttal skill do?

Use when a Journal of Public Economics (JPubE) decision letter arrives (revision or reject) and a response strategy, response letter, or appeal decision is needed. Structures the revision and response for single-anonymized specialist review; it does not redo the analysis (route to the relevant jpube-* skill).

How do I install it?

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