Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses 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…
Install Jms Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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/Journal-of-Management-Studies-Skills/skills/jms-review-process .claude/skills/jms-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 "jms-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-review-process into .claude/skills/jms-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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/Journal-of-Management-Studies-Skills/skills/jms-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 jms-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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/Journal-of-Management-Studies-Skills/skills/jms-review-process .agents/skills/jms-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 "jms-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-review-process into .agents/skills/jms-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 jms-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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/Journal-of-Management-Studies-Skills/skills/jms-review-process .cursor/skills/jms-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 "jms-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-review-process into .cursor/skills/jms-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 Journal-of-Management-Studies-Skills/skills/jms-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 jms-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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/Journal-of-Management-Studies-Skills/skills/jms-review-process .gemini/skills/jms-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 "jms-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-review-process into .gemini/skills/jms-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 jms-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 jms-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/Journal-of-Management-Studies-Skills/skills/jms-review-process .github/skills/jms-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 "jms-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-review-process into .github/skills/jms-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 jms-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 jms-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/Journal-of-Management-Studies-Skills/skills/jms-review-process .opencode/skills/jms-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 "jms-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-review-process into .opencode/skills/jms-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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
jms-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 629 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Works in 5 steps: Submission & routing. A fully anonymised… → Desk decision. Manuscripts that are… → External peer review. Typically two or… → …
- You need to understand
- SKILL.md covers When to trigger, How JMS review works (durable…, JMS is developmental and… and Reading the decision letter, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jms Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Peer review. 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
- You need to understand
- Set expectations for the Journal of Management Studies (JMS) editorial and peer-review process — desk screening
- Double-blind developmental review
- Reading a decision letter
Example prompts
- “/jms-review-process”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Submission & routing. A fully anonymised manuscript enters via ScholarOne (mc.manuscriptcentral.com/jmstudies). A General Editor (or an…
- Desk decision. Manuscripts that are off-fit, that lack a clear theoretical contribution, that are out of scope, or that are not engaged…
- External peer review. Typically two or more reviewers in the focal conversation evaluate the theoretical contribution and the rigor of the…
- Editor synthesis. The handling editor weighs the reviews, forms an independent judgment, and writes the decision letter. The editor's…
- Decision. Common outcomes: reject; reject with possible resubmission as new; major revision (R&R); minor revision; (rarely) accept. A…
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
Jms Review Process loads about 1.3k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 629 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). 629 words, ~1,318 tokens.
Download SKILL.mdSave it as
.claude/skills/jms-review-process/SKILL.md (or your agent's skills folder).- name
- jms-review-process
- description
- 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).
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)
- 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.
- Desk decision. Manuscripts that are off-fit, that lack a clear theoretical contribution, that are out of scope, or that are not engaged with a management/organization conversation may be desk-rejected without external review. The most common desk-reject reason is "no clear contribution to theory."
- External peer review. Typically two or more reviewers in the focal conversation evaluate the theoretical contribution and the rigor of the method — held to the same bar whether the paper is quantitative or qualitative.
- Editor synthesis. The handling editor weighs the reviews, forms an independent judgment, and writes the decision letter. The editor's letter — not a vote count — drives the outcome.
- Decision. Common outcomes: reject; reject with possible resubmission as new; major revision (R&R); minor revision; (rarely) accept. A first-round acceptance is essentially unheard of.
JMS is developmental and pluralist
JMS's review culture is developmental and method-pluralist: an R&R is an invitation to improve the paper over (often) multiple rounds, and reviewers will push hardest on the theoretical contribution. For qualitative work, expect demands for a sharper model, clearer data-to-theory transparency, and a tighter contribution — not a demand to "add hypotheses." For quantitative work, expect endogeneity, CMB, and robustness pushback plus a "deepen the mechanism" demand. Treat an R&R as a serious opportunity, not a near-acceptance.
Show full SKILL.md (257 more words)Show less
Reading the decision letter
- Find the editor's priorities first. The handling editor's letter signals which reviewer points are essential vs. optional; address the editor's framing above all.
- Distinguish fatal from fixable. If the core contribution or identification concern is fatal and unaddressable, an honest reframe (or a different paper) beats a doomed revision.
- Gauge encouragement. "We see promise" + major revision signals a real path; "does not make a sufficient theoretical contribution" signals reject.
- Count the asks by category. Map every reviewer point to: theory / method / analysis / framing / writing — this becomes the plan that feeds
jms-rebuttal.
Planning the revision
- Decide whether you can meet the theoretical-contribution demands; if not, no method fix will save the revision.
- Scope new analyses, data, or fieldwork the reviewers imply and whether they are feasible in the window.
- Identify where reviewers conflict; plan to surface the conflict for the editor rather than silently siding with one.
Checklist
- Decision type identified (R&R major/minor, reject-resubmit, reject)
- The handling editor's priorities extracted and ranked above individual reviewer asks
- Every reviewer comment categorised (theory / method / analysis / framing / writing)
- Fatal vs. fixable concerns separated honestly
- Feasibility of demanded new theory/data/analysis assessed against the deadline
- Reviewer conflicts noted for the editor's attention
Anti-patterns
- Treating an R&R as a near-acceptance and making only cosmetic changes
- Treating an R&R as a rejection and walking away from a viable path
- Counting reviewer votes instead of reading the handling editor's letter
- Responding to a qualitative-paper review as if it demanded hypotheses
- Starting the response letter before mapping and planning the revision
Output format
【Decision type】R&R(major/minor) / reject-resubmit / reject
【Editor's priorities】1… 2… 3…
【Comment map】theory:[…] method:[…] analysis:[…] framing:[…] writing:[…]
【Fatal vs. fixable】…
【New work needed】theory / data / analysis — feasible? …
【Reviewer conflicts】…
【Next step】jms-rebuttal (plan revisions, then draft response)© 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 Journal-of-Management-Studies-Skills/skills/jms-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jms 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 |
|---|---|---|---|---|---|---|
| Jms Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
Similar skills
Scholar Evaluation
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
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…
Related
Categories
Questions about Jms Review Process
What does Jms Review Process do?
A skill your agent uses 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…. Jms Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Jms Review Process?
Jms Review Process fits situations like: you need to understand; set expectations for the Journal of Management Studies (JMS) editorial and peer-review process — desk screening; double-blind developmental review; reading a decision letter.
How do I install Jms Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-review-process -a claude-code`. Or copy the skill folder (Journal-of-Management-Studies-Skills/skills/jms-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jms-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Jms Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-review-process -a codex`. Or copy the skill folder (Journal-of-Management-Studies-Skills/skills/jms-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jms-review-process in your project. Codex loads it when a task matches its description.
Can I use Jms 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 jms-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/jms-review-process, .gemini/skills/jms-review-process, .github/skills/jms-review-process and .opencode/skills/jms-review-process in your project.
What does Jms Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Jms Review Process is instructions for the agent only.
Does Jms 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 Jms 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 Jms Review Process use?
Jms 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 Jms Review Process use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Jms Review Process?
Skills that share tags, products or a category with Jms Review Process: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jms Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.