From ors-skills
Explains the Operations Research journal editorial process, including area-editor routing, soft double-anonymous review, decision types, and how to read a decision letter.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ors-skills:ors-review-processThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- You want to understand how *Operations Research* routes and decides on a manuscript.
Operations Research uses a departmental structure run by INFORMS:
ors-topic-selection).Typical decision types and what they signal:
| Decision | Read it as |
|---|---|
| Reject (or desk reject) | Fit/area mismatch, thin methodological contribution, or a fatal flaw |
| Major revision | The core idea has promise; substantial proof/experiment work expected |
| Minor revision | Results stand; address specific gaps and presentation |
| Accept | Rare on first round; expect at least one revision cycle |
When you read the letter:
【Decision】reject / major / minor / accept
【Editor synthesis】binding points (proof vs. exposition vs. reproducibility)
【Identity map】reviewers blind to you; you see AE-area only
【Conference/copyright】flagged?
【Plan】what to fix, in priority order
【Next step】ors-rebuttal
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin ors-skillsExplains the IJOC review pipeline: Area-Editor desk-reject gate, undisclosed associate editor, single-blind reviewing, decision types, and sibling journal fit. Sets expectations and strategy; does not draft rebuttals.
Explains Organization Science's decentralized senior-editor review model, conflict-of-interest routing, double-blind submission preparation, and how to interpret decision letters.
Runs the final pre-submission preflight for Operations Research manuscripts, covering anonymization, area selection, reviewer recommendation, contribution statement, page limits, and code/data deposit plan.