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

Rje Review Process

ASecurity

Use to understand and plan around The RAND Journal of Economics (RJE) review pipeline — the upfront editor screen (possible desk reject), peer review by two anonymous referees, and a final read by the handling Editor. Sets expectations and shapes a submission that clears the first screen.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Rje Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: rje-review-process
description: Use to understand and plan around The RAND Journal of Economics (RJE) review pipeline — the upfront editor screen (possible desk reject), peer review by two anonymous referees, and a final read by the handling Editor. Sets expectations and shapes a submission that clears the first screen.
---

# Review Process (rje-review-process)

## When to trigger

- You want to know what happens after you press submit on Wiley Research Exchange
- You are deciding how to pitch the cover letter and front-load the contribution
- You are gauging desk-reject risk before paying the submission fee

## How RJE review works (verified 2026-06-01)

RJE uses an **editor-screened, then two-anonymous-referee** model (source: rje.org/submissions.html):

1. **Editor screen.** Each manuscript is first assigned to an Editor on the Board of Editors who **quickly reviews it and may desk-reject** before any refereeing. The current **Editor-in-Chief is Craig A. Bond (RAND)**; handling Editors include IO specialists such as Gary Biglaiser, Ying Fan, Alessandro Gavazza, Jean-François Houde, Julian Wright, and Jidong Zhou. Because the front screen is explicit and fast, the **first page of the article and the cover letter must make the IO contribution legible immediately**.
2. **Two anonymous referees.** Manuscripts that survive the screen go to **two referees who are anonymous to authors**. (Whether author identity is concealed from referees — single vs double blind — is **待核实**; do not assume double-blind.)
3. **Handling Editor decision.** The handling Editor reads the reports and the article and issues the decision (reject / R&R / rare accept).

## What clears the screen at the IO flagship

- A **first-order industrial-organization question** stated in the opening paragraph (market structure, competition/antitrust, regulation, firm strategy, the economics of organizations) — not a general-micro or macro question.
- A **credible method matched to the question**: a well-specified structural model (demand/supply, entry, auctions) or a clean reduced-form design off a policy/merger shock.
- **Respect for the hard page caps** (40/50 pp) — an overlong submission signals undisciplined exposition to a screening Editor.
- A cover letter that names the market, the method, and the **headline result and welfare/policy lesson** in a few sentences.

## Anti-patterns

- Treating RJE like a general-interest journal and burying the IO hook
- Assuming a slow, multi-reviewer process — RJE leans on a **fast editor screen + two referees**
- Asserting the review is double-blind and writing the article around that (待核实)
- A defensive, sprawling cover letter the screening Editor cannot skim

## Output format

```
【Stage model】editor screen → 2 anonymous referees → handling Editor
【Desk-reject risk】high / medium / low + why
【IO hook on page 1?】[Y/N]
【Cover letter】names market + method + headline + policy lesson? [Y/N]
【Next step】rje-submission (preflight) or rje-contribution-framing (sharpen hook)
```

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 →