Agent skill · Code Review & Quality

jms-review-process

Use when you need to understand or set expectations for the Journal of Management Studies (JMS) editorial and peer-review process — desk screening, double-blind developmental review, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (jms-rebuttal).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-review-process --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Journal-of-Management-Studies-Skills/skills/jms-review-process/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Understanding the Review Process (jms-review-process) ## When to trigger - Before submitting, to calibrate expectations about timeline, desk-reject odds, and decision types - A decision letter arrived and you need to interpret it (R&R vs. reject; major vs. minor) - You are unsure how much weight reviewers vs. the handling editor carry - You want to plan a revision strategy before drafting the response (then go to `jms-rebuttal`) > Editorial structure, named editors, and exact turnaround change; verify the current team and policies on the official Wiley/SAMS pages. As of `检索于 2026-06;以官网为准`: JMS uses **double-blind** review; the editorial office is at **Durham University**; the General Editors/Editor-in-Chief and exact timelines are **待核实** unless quoted from an official page at submission time. The norms below are durable. ## How JMS review works (durable norms) 1. **Submission & routing.** A fully anonymised manuscript enters via ScholarOne (mc.manuscriptcentral.com/jmstudies). A General Editor (or an Associate/handling Editor) screens it and, if it passes, routes it to a handling editor in the relevant area. 2. **Desk decision.** Manuscripts that are off-fit, that lack a clear

What's inside
Steps it walks through
  1. When to trigger
  2. How JMS review works (durable norms)
  3. JMS is developmental and pluralist
  4. Reading the decision letter
  5. Planning the revision
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jms-review-process skill do?

Use when you need to understand or set expectations for the Journal of Management Studies (JMS) editorial and peer-review process — desk screening, double-blind developmental review, and reading a decision letter. Explains the process and how to read decisions; it does not draft the response letter (jms-rebuttal).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-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.

Keep going