Agent skill · Code Review & Quality

red-rebuttal

Use when planning the response-to-referees after a Review of Economic Dynamics (RED) revise-and-resubmit — structuring a point-by-point reply for a single-anonymized, two-referee process, prioritizing model/quantitative concerns, and remembering that second-and-later resubmissions are exempt from the submission fee. Strategy; it does not write the paper.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill red-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: Review-of-Economic-Dynamics-Skills/skills/red-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 Strategy for RED (red-rebuttal) ## When to trigger - An R&R has arrived from RED and you are planning the revision and reply - Reconciling comments from the (minimum) two referees and the editor - Deciding how to handle requests that touch the model, calibration, or code archive ## How to respond at RED - **Point-by-point, per referee.** RED uses **single-anonymized** review with at least **two referees**; structure a clear, numbered response to each, plus a short letter to the Coordinating Editor summarizing the main changes. Quote each comment, then state the change and where it lives in the revised paper. - **Lead with the model/quantitative concerns.** Referees at a dynamic-economics journal care most about whether the **mechanism**, **assumptions/regularity conditions**, **calibration discipline**, and **numerical accuracy** hold up. Address those first; presentation comments after. - **Re-run and re-archive.** If you change the model, calibration, or estimation, **re-run everything** and update the data/code archive (and its readme.txt: seeds, execution order, runtime), since RED's code-first culture means reviewers expect the archive to track the revision. - **Fee

What's inside
Steps it walks through
  1. When to trigger
  2. How to respond at RED
  3. Checklist
  4. Anti-patterns
  5. Rerun rule
  6. Response-letter skeleton for a RED R&R
  7. Frequent RED referee demands and how to absorb them
  8. Triage order for the revision
  9. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the red-rebuttal skill do?

Use when planning the response-to-referees after a Review of Economic Dynamics (RED) revise-and-resubmit — structuring a point-by-point reply for a single-anonymized, two-referee process, prioritizing model/quantitative concerns, and remembering that second-and-later resubmissions are exempt from the submission fee. Strategy; it does not write the paper.

How do I install it?

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