ors-review-process
Use when navigating the Operations Research (OR) editorial process — the departmental area-editor routing, the soft double-anonymous model with asymmetric transparency, decision types, and how to read a decision letter from the handling Area Editor. Explains how review works and how to read a decision; it does not draft the response (ors-rebuttal) or run the preflight (ors-submission).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-review-process --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Review Process (ors-review-process) ## When to trigger - You want to understand how *Operations Research* routes and decides on a manuscript. - A decision letter arrived and you need to parse roles, signals, and the path forward. - You are unsure who sees your identity and whose names you can see. ## How OR review is organized *Operations Research* uses a **departmental** structure run by **INFORMS**: - **Area-editor routing.** At submission you select one of the journal's named editorial areas; the manuscript is handled within that department by an **Area Editor (AE-area)**, who assigns an **Associate Editor**, who recruits **reviewers**. Areas publish **Area Editors' Statements** defining scope, so a mismatched area can cost you a re-route (see `ors-topic-selection`). - **Soft double-anonymous with asymmetric transparency.** Author names are omitted from the submission. **Reviewers cannot see authors.** The **Area Editor and Associate Editor can** see author names. Distinctively, **authors can see the handling Area Editor's name** but **not** the Associate Editor or reviewers. This asymmetry distinguishes OR from fully blinded or fully open models. ## Reading the decision lette
- When to trigger
- How OR review is organized
- Reading the decision letter
- Expectations as an OR author
- Anti-patterns
- Output format
What does the ors-review-process skill do?
Use when navigating the Operations Research (OR) editorial process — the departmental area-editor routing, the soft double-anonymous model with asymmetric transparency, decision types, and how to read a decision letter from the handling Area Editor. Explains how review works and how to read a decision; it does not draft the response (ors-rebuttal) or run the preflight (ors-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-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.