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

Jm Review Process

ASecurity

Use when understanding how Journal of Marketing (JM) review and decisions work — the double-anonymized process, the Coeditor structure, the substantive-and-relevance evaluation bar, and how to read a decision letter. Explains the process and reads the letter; it does not draft the response (jm-rebuttal).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsaws

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jm-review-process --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jm Review Process?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jm-review-process
description: Use when understanding how Journal of Marketing (JM) review and decisions work — the double-anonymized process, the Coeditor structure, the substantive-and-relevance evaluation bar, and how to read a decision letter. Explains the process and reads the letter; it does not draft the response (jm-rebuttal).
---

# Review Process (jm-review-process)

## When to trigger

- Before submitting, to set realistic expectations about JM review
- A decision letter arrived and you need to interpret it before responding
- You are unsure who decides at JM and what reviewers are told to weigh
- You want to know what "conditional acceptance" triggers (replication packet)

## How JM review works

- **Double-anonymized**: identities of authors and reviewers are concealed from each other. Keep all rounds anonymized; never reveal yourself in responses or revised files.
- **Decision authority**: the handling **Editor is the final decision authority**. Under EiC Jan-Benedict E.M. Steenkamp, manuscripts are handled by one of four **Coeditors** — Marc Fischer (Cologne), Kelly L. Haws (Vanderbilt), Maura L. Scott (Arizona State), Rebecca J. Slotegraaf (Indiana). Your keyword/area choices influence routing.
- **What reviewers weigh**: JM's gatekeeping criterion is **substantive impact** — does the paper offer compelling new insight into an important real-world marketing question, *with* managerial/policy/societal relevance? Reviewers also screen for scope: general-management papers, methods-for-their-own-sake papers, and incremental/new-context replications are out of scope. Expect probes on identification, exact-statistic reporting, and whether the magnitude matters.
- **Integrity**: manuscripts are screened with iThenticate; no concurrent submission.

## Likely decisions

| Decision                 | What it means                                                       |
|--------------------------|---------------------------------------------------------------------|
| Desk reject              | Out of scope, not substantive enough, or relevance absent           |
| Reject (after review)    | Substantive contribution or identification judged insufficient      |
| Major revision (R&R)     | Promising substantive core; significant work required               |
| Minor revision           | Substantively sound; targeted fixes                                 |
| Conditional acceptance   | Triggers the **JM Dataverse replication packet** + Data Availability Statement |

First-round acceptances are essentially unheard of; a well-run R&R is the realistic best case.

## Reading the decision letter

- Read the **Coeditor letter first** — it states the path to acceptance and which concerns are decisive ("must address") versus secondary.
- Cluster reviewer comments by theme: **substantive contribution**, **identification/analysis**, **managerial relevance**, **positioning**, **exposition**.
- Flag any comment touching the **substantive-novelty** or **relevance** bar as top priority — these are JM's gatekeeping criteria.
- Note transparency expectations early: if you are near conditional acceptance, prepare the **JM Dataverse** packet (data + code, or qualitative materials) and confirm preregistration links/attestation.
- Distinguish requests that need **new data/analysis** from those needing **reframing** — they have very different timelines.

## At conditional acceptance

Deposit the replication packet to **JM's Dataverse** (raw data, analysis programs/scripts; qualitative materials for qualitative work), accessible to the **processing Editor** but not reviewers, and ensure the **Data Availability Statement** is on the title page. (JM does not specify a dedicated Data-Editor verification step the way JMR does — 待核实.)

## Checklist

- [ ] Coeditor letter parsed: decisive vs. secondary concerns identified
- [ ] Reviewer comments clustered by theme
- [ ] Substantive-novelty and relevance comments flagged as top priority
- [ ] New-data vs. reframing requests separated (timeline planning)
- [ ] Conditional-acceptance transparency steps anticipated (JM Dataverse + DAS)

## Anti-patterns

- Treating all reviewer comments as equal weight, ignoring the Coeditor's priorities.
- De-anonymizing yourself in a response or revised file.
- Reading a major R&R as a near-accept and doing superficial edits.
- Deferring replication-packet prep until after conditional acceptance scrambles the timeline.

## Output format

```
【Decision】desk reject / reject / major R&R / minor / conditional accept
【Coeditor priorities】must-address: [...]; secondary: [...]
【Comment clusters】substantive / identification / relevance / positioning / exposition
【Gatekeeper flags】novelty + relevance comments: [...]
【New data vs. reframing】[...]
【Transparency next】JM Dataverse + DAS readiness: [...]
【Next step】jm-rebuttal
```

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 →