Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Red Review Process

ASecurity

Use to understand and plan around the Review of Economic Dynamics (RED) editorial process — the editor desk/suitability screen, single-anonymized refereeing with a minimum of two reviewers, and SED's fast ~two-month average post-desk turnaround. Sets expectations and timelines; it is not the submission preflight (see red-submission).

1,052 stars
0 votes
0 copies
0 views
Added 6/6/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill red-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Red Review Process?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Red Review Process
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-red-review-process/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-red-review-process)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: red-review-process
description: Use to understand and plan around the Review of Economic Dynamics (RED) editorial process — the editor desk/suitability screen, single-anonymized refereeing with a minimum of two reviewers, and SED's fast ~two-month average post-desk turnaround. Sets expectations and timelines; it is not the submission preflight (see red-submission).
---

# 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.** The SED advertises fast reviews, targeting roughly a **two-month average
  post-desk turnaround** — RED positions itself among the more efficient journals in economics.
- **Coordinating Editor.** **Loukas Karabarbounis** (University of Minnesota / Minneapolis Fed) is RED's
  Coordinating Editor (the editor-in-chief equivalent). *(Some third-party sources are outdated on this — 待核实 elsewhere, but SED's own page is authoritative.)*

## Planning implications

- Single-anonymized means **keep self-citations and acknowledgments natural** — no double-blind scrubbing.
- The fast-turnaround target rewards a **complete, runnable** submission with replication discipline
  already in place; do not submit a paper whose code archive does not yet exist.
- Plan around a **post-desk** clock that starts only after the suitability screen and the fee.

## Checklist

- [ ] Manuscript is **not** anonymized (single-anonymized model)
- [ ] Paper is in-scope and complete enough to clear the desk screen quickly
- [ ] Expectations set for ≥2 referees and a ~two-month post-desk target
- [ ] Replication materials staged so a fast acceptance is not bottlenecked

## Anti-patterns

- Double-blind-scrubbing a manuscript for a single-anonymized journal
- Expecting the ~two-month clock to cover the desk screen or fee step
- Treating slow-journal habits (thin appendix, no code) as acceptable here

## Supplementary resources

- [`red-submission`](../red-submission/SKILL.md) — the pre-submission preflight
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review-model and timing sources

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →