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

Jmr Review Process

ASecurity

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.

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 jmr-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jmr Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jmr-review-process
description: 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.
---

# 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. (The by-domain routing chart itself is not published — 待核实 — so this is inferred from the masthead structure.)

> Transition note: Rebecca Hamilton (Georgetown) is EIC of record through 30 June 2026; Raphael Thomadsen's incoming team (WashU) has handled **new** submissions since 1 April 2026. Authors submitting now are effectively reviewed by the incoming team.

## The stages

1. **Initial editorial evaluation** — the editor screens for scope, fit, and conformance. Out-of-scope or non-conforming papers can be **desk-rejected without peer review** (e.g., wrong venue, exceeds 50 pages, missing exact-statistics/transparency requirements).
2. **Double-anonymized peer review** — identities of both authors and reviewers are concealed from both parties.
3. **Decision** — to reach a **Revise or Accept** decision, the manuscript requires **two independent reviews**. The editor has final authority and integrates the reviews with their own read.

## Read the decision letter by genre

- **Rigor-bar objections** — "identification is not convincing," "the manipulation is confounded," "report effect sizes / exact p-values," "the instrument is weak." These are often addressable with new analyses, studies, or Web Appendix material.
- **Substance-bar objections** — "the contribution is incremental," "what do we learn?" These are harder; they may require reframing (`jmr-contribution-framing`) or additional studies, not just robustness.
- **Both bars** — JMR's dual standard means a paper can be methodologically clean yet rejected for thin contribution, or interesting yet rejected for weak identification. Diagnose which bar the letter is really about.

## Set expectations

- First-round **accepts are essentially unheard of**; a Revise (R&R) is a strong outcome.
- Expect multiple rounds; reviewers are domain experts who will probe identification, process evidence, and exact-statistics reporting.
- A desk reject is usually about fit or conformance, not a verdict on quality — re-target or fix conformance.

## Anti-patterns

- Treating a desk reject as a content verdict (it is usually scope/fit/format).
- Reading only the reviews and ignoring the **editor's** framing of which concerns are pivotal.
- Assuming one enthusiastic review is enough — two independent reviews gate Revise/Accept.

## Output format

```text
[Target] JMR
[Decision] desk-reject / reject / R&R / minor
[Routing] likely Coeditor/AE domain
[Pivotal bar] rigor / substance / both
[Editor's framing] key asks ...
[Tractability] addressable via analysis/studies vs. reframe
[Next skill] jmr-rebuttal (if R&R)
```

## Resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md)
- [`../../resources/external_tools.md`](../../resources/external_tools.md)

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 →