Video Understand
calesthio/OpenMontage
Understand video content locally using ffmpeg frame extraction and Whisper transcription.
A skill your agent uses to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, double-anonymized refereeing, the cross-department fit bar…
MITAuto-check passed
Install Mgsci Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mgsci-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Management-Science-Skills/skills/mgsci-review-process .claude/skills/mgsci-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-process into .claude/skills/mgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mgsci-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mgsci-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Management-Science-Skills/skills/mgsci-review-process .agents/skills/mgsci-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-process into .agents/skills/mgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mgsci-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mgsci-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Management-Science-Skills/skills/mgsci-review-process .cursor/skills/mgsci-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-process into .cursor/skills/mgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mgsci-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Management-Science-Skills/skills/mgsci-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mgsci-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Management-Science-Skills/skills/mgsci-review-process .gemini/skills/mgsci-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-process into .gemini/skills/mgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mgsci-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mgsci-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Management-Science-Skills/skills/mgsci-review-process .github/skills/mgsci-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-process into .github/skills/mgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mgsci-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills mgsci-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Management-Science-Skills/skills/mgsci-review-process .opencode/skills/mgsci-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mgsci-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Management-Science-Skills/skills/mgsci-review-process into .opencode/skills/mgsci-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mgsci-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
mgsci-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, double-anonymized refereeing, the cross-department fit bar…
- Works in 4 steps: Department/area routing. A submission is… → Desk screen. The Department Editor, and… → External review. If the manuscript… → …
- Understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen
- SKILL.md covers When to trigger, How a submission flows, The cross-department fit bar and Turnaround, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Mgsci Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
Example prompts
- “/mgsci-review-process”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Department/area routing. A submission is channeled into a specific Department (e.g., Accounting; Behavioral Economics and Decision…
- Desk screen. The Department Editor, and possibly an Associate Editor, first evaluates whether the manuscript is a good fit for the…
- External review. If the manuscript passes the initial screen, an Associate Editor recruits reviewers and later recommends to the…
- Decision. The Department Editor recommends; the Editor-in-Chief (Christoph Loch, term 2024–2026) provides final oversight and…
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Mgsci Review Process loads about 1.5k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 704 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 704 words, ~1,480 tokens.
Download SKILL.mdSave it as
.claude/skills/mgsci-review-process/SKILL.md (or your agent's skills folder).- name
- mgsci-review-process
- description
- 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).
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
- 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.
- 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 Operations Research / M&SOM / Marketing Science") or insufficient rigor/contribution.
- External review. If the manuscript passes the initial screen, an Associate Editor recruits reviewers and later recommends to the Department Editor. Review is double-anonymous — neither side sees the other's identity.
- 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 states that it strives to provide high-quality feedback to 90% of authors within 90 days. If a paper is sent to reviewers, authors receive a Department Editor decision within 65 days on average. Acceptance does not end the workflow: accepted numerical/computational papers still need the Code and Data Disclosure materials required before production.
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.
Show full SKILL.md (289 more words)Show less
Desk-reject reason map
Because Management Science is the multidisciplinary INFORMS flagship, the desk screen is run by a Department Editor enforcing that department's rigor bar and the cross-department fit test.
| Desk-reject reason | What it signals | Implied next move |
|---|---|---|
| "Better suited to a sister INFORMS journal" | A routing verdict, not necessarily quality | Re-aim or target the named journal |
| "Contribution does not clear the bar" | Rigor present, decision insight thin | Reframe; do not just resubmit |
| "No clear home department" | Ambiguous-fit; arbitration redirected it | Name a department + the bridge |
Worked micro-example (illustrative): two letters
Letter A: "Interesting model, but the algorithmic contribution would be better appreciated at Operations Research." This is a routing verdict — the work may be excellent, just mis-homed; do not appeal. Letter B: "The identification does not rule out selection, and the managerial implication is unclear." This is a substantive reject on two flagship bars (empirical leverage and a decision-relevant contribution); a major reframe plus a stronger design is needed. Distinguishing routing from substantive rejects decides whether you re-aim or rebuild.
Referee-pushback patterns and the venue-specific fix
- "Which department is this, and does it clear that bar?" Make the home department explicit at submission so the right editor desk-screens it; confirm the design meets that department's standard.
- "This belongs at a sister INFORMS journal." Surface the cross-department travel that distinguishes a flagship paper.
Calibration anchor
Turnaround targets, department rosters, and disclosure requirements evolve — treat the values above as current official guidance and re-check the source map before submission or appeal advice.
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)© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Management-Science-Skills/skills/mgsci-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Mgsci Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mgsci Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Video Understandcalesthio/OpenMontage | 66k | — | ~841 | Automated safety check: Pass | AGPL-3.0 | |
| Understand ExplainEgonex-AI/Understand-Anything | 86k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Understanding by Design PlannerTHU-MAIC/OpenMAIC | 40k | — | ~548 | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Information Security Manager Iso27001davila7/claude-code-templates | 32k | 1 repos | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
Understanding by Design Planner
THU-MAIC/OpenMAIC
Plans an OpenMAIC lesson or course series by backward design: enduring understandings and essential questions first, then performance evidence, then learning activities.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Information Security Manager Iso27001
davila7/claude-code-templates
Senior Information Security Manager specializing in ISO 27001 and ISO 27002 implementation for HealthTech and MedTech companies.
Understand Issue
mastra-ai/mastra
Investigate a GitHub issue or reported bug the way a seasoned maintainer would — form an independent model before reading the thread's theories, trace the mechanism and history, verify the…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Mgsci Review Process
What does Mgsci Review Process do?
A skill your agent uses to understand how Management Science (INFORMS) review and decisions work — the Department/area-editor desk screen, double-anonymized refereeing, the cross-department fit bar…. Mgsci Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Mgsci Review Process?
Mgsci Review Process fits situations like: 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.
How do I install Mgsci Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a claude-code`. Or copy the skill folder (Management-Science-Skills/skills/mgsci-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/mgsci-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Mgsci Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a codex`. Or copy the skill folder (Management-Science-Skills/skills/mgsci-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/mgsci-review-process in your project. Codex loads it when a task matches its description.
Can I use Mgsci Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mgsci-review-process, .gemini/skills/mgsci-review-process, .github/skills/mgsci-review-process and .opencode/skills/mgsci-review-process in your project.
What does Mgsci Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Mgsci Review Process is instructions for the agent only.
Does Mgsci Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Mgsci Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Mgsci Review Process use?
Mgsci Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Mgsci Review Process use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Mgsci Review Process?
Skills that share tags, products or a category with Mgsci Review Process: Video Understand (calesthio/OpenMontage, 66k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars), Understanding by Design Planner (THU-MAIC/OpenMAIC, 40k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Mgsci Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.