Use when polishing prose for a Journal of Marketing Research (JMR) manuscript — a third-person 200-word abstract, AMA author-year citations, the exact-statistics number conventions, and a front-loaded research argument that clears JMR's dual bar without drifting into managerial Journal-of-Marketing framing. Late-stage polish only.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jmr-writing-style --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Jmr Writing Style?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-jmr-writing-style)More formats (shields.io, HTML) on the badges page.
---
name: jmr-writing-style
description: Use when polishing prose for a Journal of Marketing Research (JMR) manuscript — a third-person 200-word abstract, AMA author-year citations, the exact-statistics number conventions, and a front-loaded research argument that clears JMR's dual bar without drifting into managerial Journal-of-Marketing framing. Late-stage polish only.
---
# Writing Style (jmr-writing-style)
## When to trigger
- The abstract, intro, or prose buries the contribution
- Citations and numbers are not in AMA style
- The writing reads as a managerial pitch rather than a research argument
- Final language polish before submission (after the contribution is settled)
## JMR-specific style rules
- **Abstract**: **200 words maximum, written in the third person.** It should state the marketing question, the approach (experiment/model), the key result, and the contribution — not a teaser. (Title **≤ 25 words**; up to **8 keywords**.)
- **Citations**: **AMA author-year** style — "Thorelli (1960)" / "(Thorelli 1960)"; list all authors up to three, "et al." for four or more. There is **no reference cap**, so cite both relevant behavioral and modeling work. Not APA-numeric.
- **Numbers in prose**: report **exact p-values to three digits**, with **no leading zero** (`p = .032`, `.97`), and **no more than three decimals**; report effect sizes alongside significance. Mirror the table conventions in the text.
- **Formatting**: 12-point Times New Roman (or 12-point LaTeX font), double-spaced (tables/references may be single-spaced), 1-inch margins; no page/line numbers, no headers/footers. Keep the print article within **50 pages**.
## Write a front-loaded research argument
- Open with the **marketing phenomenon and the research question**, then the gap/tension, then what you do and find — the contribution should be visible on page one without the appendix.
- Use **active voice** and direct sentences; explain the mechanism or identification in plain terms before the technical detail.
- Keep it a **research** contribution. Managerial implications belong in the discussion as a consequence of the findings, not as the lead — leading with "what managers should do" reads as a *Journal of Marketing* paper.
- Match register to genre: behavioral papers narrate the process and converging studies; modeling papers state the question, the model intuition, then the identification.
## AI-content disclosure
If any AI-generated content is used, it must be **identified in the main document** (e.g., in Methods) and noted in the **Acknowledgments** — write these in now so the submission conforms.
## Anti-patterns
- A first-person or results-teaser abstract, or one over 200 words.
- APA-numeric citations; "p < .05" or asterisks in prose; leading zeros before decimals.
- Managerial-pitch framing that hides the research contribution.
- Polishing prose before the contribution and identification are settled.
## Output format
```text
[Target] JMR
[Abstract] <=200 words, third person, states contribution: pass/fix
[Citations] AMA author-year: pass/fix
[Numbers] 3-digit p, no leading zero, <=3 decimals, effect sizes: pass/fix
[Argument] front-loaded, research-first (not managerial): pass/fix
[AI disclosure] present if used
[Next skill] jmr-submission
```
## Resources
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md)
- [`../../resources/external_tools.md`](../../resources/external_tools.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!