Agent skill · Code Review & Quality

arecon-review-process

Use when calibrating expectations for the Annual Review of Economics (ARE) Editorial Committee review cycle on an invited article — what happens after delivery, who reviews, the accuracy/rigor/balance bar, and the annual-volume timeline. Sets expectations; it does not run the delivery preflight (arecon-submission) or draft the response letter (arecon-revision).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill arecon-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: Annual-Review-of-Economics-Skills/skills/arecon-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 — What to Expect (arecon-review-process) ## When to trigger - The commissioned draft is delivered and you want to know what happens next - You are unsure whether an invited review is auto-accepted (it is not) and what it is judged on - You need to plan around the annual-volume production schedule - A coauthor expects journal-style turnaround and you must reset that to the Committee cadence ## How an invited ARE review is evaluated Being invited gets your draft *reviewed*, not *accepted*. After delivery, the Editorial Committee assesses the manuscript for **accuracy, rigor, and balance**, and may route it to **another Committee member or an external expert** as appropriate (检索于 2026-06;以官网为准). The bar is the review-article bar, not the primary-research bar: | Stage | What happens | What it tests | |-------|-------------|---------------| | Commissioning | Committee invites the topic/author; scope is set | fit, author standing, ARE-shaped topic | | Delivery | author submits the invited draft in the commissioned workflow | completeness, format, declarations | | Committee/expert review | a Committee member and/or external referee read it | accuracy, rigor, balance, acce

What's inside
Steps it walks through
  1. When to trigger
  2. How an invited ARE review is evaluated
  3. Timeline reality
  4. What referees push on (and how to pre-empt)
  5. Checklist
  6. Anti-patterns
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the arecon-review-process skill do?

Use when calibrating expectations for the Annual Review of Economics (ARE) Editorial Committee review cycle on an invited article — what happens after delivery, who reviews, the accuracy/rigor/balance bar, and the annual-volume timeline. Sets expectations; it does not run the delivery preflight (arecon-submission) or draft the response letter (arecon-revision).

How do I install it?

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