Agent skill · Code Review & Quality

jmr-review-process

Use when understanding how the Journal of Marketing Research (JMR) review process works — initial editorial evaluation and possible desk rejection, double-anonymized review, the EIC-plus-Coeditor domain-routing model, the requirement of two independent reviews to reach a Revise/Accept decision, and how to read a JMR decision letter. Sets expectations; jmr-rebuttal drafts the response.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmr-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-Marketing-Research-Skills/skills/jmr-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 JMR Review Process (jmr-review-process) ## When to trigger - Before submitting, to set realistic expectations for timing and decisions - After a decision letter, to interpret what the editor and reviewers are signaling - You are unsure how JMR routes papers or how many reviews are required - You want to understand the difference between a desk reject and a post-review reject ## How JMR routing works JMR uses an **EIC + Coeditor** model. A single **Editor-in-Chief** oversees a panel of **Coeditors** (currently four; the incoming 2026–2029 team has five) who handle manuscripts by **methodological/substantive domain**, alongside **Associate Editors** and an **Editorial Review Board**. This is analogous to INFORMS-style departmental routing, but organized around methodological/substantive domains rather than fixed departments. Practical implication: your domain keywords and article type at submission influence which Coeditor/AE your paper reaches, so choose them to land with an expert in your area. JMR does **not** publish a by-domain routing chart, so treat this routing guidance as a masthead-based inference rather than an official AMA rule. > Transition note: Rebe

What's inside
Steps it walks through
  1. When to trigger
  2. How JMR routing works
  3. The stages
  4. Read the decision letter by genre
  5. Set expectations
  6. First 48 hours with the letter
  7. Anti-patterns
  8. Output format
  9. Resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jmr-review-process skill do?

Use when understanding how the Journal of Marketing Research (JMR) review process works — initial editorial evaluation and possible desk rejection, double-anonymized review, the EIC-plus-Coeditor domain-routing model, the requirement of two independent reviews to reach a Revise/Accept decision, and how to read a JMR decision letter. Sets expectations; jmr-rebuttal drafts the response.

How do I install it?

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