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

Mgsci Review Process

ASecurity

Use to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, the high desk-reject rate, double-anonymized refereeing, the cross-department fit bar, 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).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Mgsci Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: mgsci-review-process
description: Use to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, the high desk-reject rate, double-anonymized refereeing, the cross-department fit bar, 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).
---

# 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; Business Strategy; Data Science; Finance; Information Systems; Operations Management; Optimization and Decision Analytics; Revenue Management & Market Analytics; Stochastic Models and Simulation). The **Department Editor owns the desk screen and the standards** for that field.
2. **Desk screen.** The Department Editor decides whether the paper goes to external review. **A high share is desk-rejected** (reported ~50–60% screened out before external review — **approximate / 待核实**), commonly on **fit** ("better suited to Operations Research / M&SOM / Marketing Science") or insufficient rigor/contribution.
3. **External review.** Papers passing screen go to roughly **2–3 reviewers**, often coordinated by an **Associate Editor** (~ figures **approximate / 待核实**). Review is **double-anonymized** — neither side sees the other's identity.
4. **Decision.** The Department Editor recommends; the **Editor-in-Chief (Christoph Loch, term 2024–2026)** provides final oversight and **cross-department arbitration** for ambiguous-fit papers.

## The cross-department fit bar

Beyond field rigor, papers are judged on whether they **belong in Management Science** versus a sister INFORMS journal. Ambiguous-fit papers spanning departments are discussed across the editorial team, and a large share are redirected. Expect "fit" to be a first-order screen, not an afterthought.

## Turnaround

The journal aims for an **ambitious turnaround** — reportedly giving high-quality feedback to ~90% of authors within ~90 days (**approximate / 待核实**, among the more aggressive commitments in top-tier business publishing). Acceptance triggers **Data and Code Disclosure verification** by the Data Editor, which adds ~17 days on average before publication.

## Reading a decision letter

- **Desk reject on fit** → re-aim (see `mgsci-topic-selection`) or target the named sister journal; usually not worth appealing.
- **Reject after review** → the contribution or rigor did not clear the bar; a major reframe is needed.
- **Major revision (R&R)** → a real opportunity; the Department Editor's framing letter signals which reviewer points are decisive. Go to `mgsci-rebuttal`.
- **Minor revision** → rare early; address precisely and quickly.

Read the **Department Editor's letter first** — it tells you which reviewer concerns are binding and which are advisory.

## Anti-patterns

- Treating a fit-based desk reject as a quality verdict (it is often a routing verdict).
- Ignoring the Department Editor's prioritization and weighting all reviewer comments equally.
- Assuming acceptance means immediate publication — disclosure verification still runs.

## Output format

```
【Stage】desk screen / under review / decision received
【Department & decider】Department Editor / AE / EiC
【Decision type】desk-reject(fit) / reject / R&R / minor
【Binding concerns】[from the DE letter]
【Next step】mgsci-rebuttal (R&R) or mgsci-topic-selection (re-aim)
```

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 →