mgsci-review-process
Use to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, double-anonymized refereeing, the cross-department fit bar, official turnaround targets, and how to read a decision letter — before or after submitting. It explains the process; it does not draft the response (mgsci-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-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 (mgsci-review-process) ## When to trigger - You want to know what happens to a submission and how long it takes - You are unsure who decides (Department Editor vs Associate Editor vs Editor-in-Chief) - A paper was desk-rejected and you need to understand why - You received a decision letter and want to read it correctly before responding ## How a submission flows 1. **Department/area routing.** A submission is channeled into a specific **Department** (e.g., Accounting; Behavioral Economics and Decision Analysis; Data Science; Entrepreneurship and Innovation; Finance; Healthcare Management; Information Systems; Market Design, Platform, and Demand Analytics; Marketing; Operations Management; Optimization and Decision Analytics; Organizations; Stochastic Models and Simulation; Strategy; Sustainability). The **Department Editor owns the desk screen and the standards** for that field. 2. **Desk screen.** The Department Editor, and possibly an Associate Editor, first evaluates whether the manuscript is a good fit for the department and has enough merit to send to reviewers. If not, the paper is returned with the editors' reasoning, commonly on **fit** ("better suited to
- When to trigger
- How a submission flows
- The cross-department fit bar
- Turnaround
- Reading a decision letter
- Desk-reject reason map
- Worked micro-example (illustrative): two letters
- Referee-pushback patterns and the venue-specific fix
- Calibration anchor
- Anti-patterns
- Output format
What does the mgsci-review-process skill do?
Use to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, double-anonymized refereeing, the cross-department fit bar, official turnaround targets, and how to read a decision letter — before or after submitting. It explains the process; it does not draft the response (mgsci-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-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.