Agent skill · Code Review & Quality

red-review-process

Use when understanding or planning around the Review of Economic Dynamics (RED) editorial process — the editor desk/suitability screen, single-anonymized refereeing with a minimum of two reviewers, and RED's fast-review orientation without promising a fixed decision date. Sets expectations and timelines; it is not the submission preflight (see red-submission).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill red-review-process --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-review-process/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

# Review Process at RED (red-review-process) ## When to trigger - Setting expectations on timing and review model before or after submitting - Understanding what the desk screen decides and what reaches referees - Planning around the single-anonymized (not double-blind) model ## How RED review works (verified) - **Desk / suitability screen first.** The editor first assesses whether the paper is suitable for RED; papers that pass are sent out for review. A clean, in-scope, dynamic-model paper clears this faster. - **Single-anonymized review.** Reviewers' identities are concealed from authors, but **author identities are visible to reviewers** — this is *not* double-blind, so you do **not** anonymize the manuscript. - **Minimum of two reviewers.** Suitable papers go to at least **two independent referees**. - **Speed is a feature, not a guarantee.** The current reviewer page asks reviewers to notify the editor if they cannot act within six weeks, and older SED newsletters report fast first-decision performance. Treat this as planning guidance, then confirm live expectations in the current author system. - **Coordinating Editor.** **Loukas Karabarbounis** (University of Minnesota / Mi

What's inside
Steps it walks through
  1. When to trigger
  2. How RED review works (verified)
  3. Planning implications
  4. Pre-review readiness
  5. Checklist
  6. Anti-patterns
  7. What fails the suitability screen
  8. Round log
  9. Who referees at a SED journal
  10. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the red-review-process skill do?

Use when understanding or planning around the Review of Economic Dynamics (RED) editorial process — the editor desk/suitability screen, single-anonymized refereeing with a minimum of two reviewers, and RED's fast-review orientation without promising a fixed decision date. Sets expectations and timelines; it is not the submission preflight (see red-submission).

How do I install it?

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