Agent skill · Documentation

jom-writing-style

Use when drafting or polishing prose for a Journal of Operations Management (JOM) empirical manuscript — front-loading the operations argument, writing for both academics and practitioners, keeping APA house style, and meeting JOM's length, formatting, and text-overlap rules.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-writing-style --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-Operations-Management-Skills/skills/jom-writing-style/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

# Writing Style for JOM (jom-writing-style) ## When to trigger - Prose is jargon-heavy, passive, or buries the operations argument - The paper reads as academic-only and ignores the practitioner audience - You need to meet JOM/Wiley formatting, length, and similarity rules - You are reconciling citations and references to APA ## Front-load the operations argument JOM readers — and ASCM's practitioner audience — want the point early. State the operations phenomenon, the puzzle, and the contribution in the first page, before the literature scaffolding. Use active voice and concrete operational language (cycle time, fill rate, supplier dependence, recall severity) rather than abstract management prose. Because the work must show **operations at the heart of the question**, every section should keep the operations phenomenon in view. ## Write for academics and practitioners JOM demands **both academic and practical relevance**. Explain operational constructs plainly, translate statistical results into operational consequences (what changes on the floor, in the network, at the bedside), and avoid theory-for-its-own-sake. A manager and a reviewer should both finish a section knowing why

What's inside
Steps it walks through
  1. When to trigger
  2. Front-load the operations argument
  3. Write for academics and practitioners
  4. Format and length rules
  5. Text-overlap discipline (enforced)
  6. Anti-patterns
  7. Prose moves JOM referees reward
  8. Return and screen triggers on writing
  9. Worked vignette: rewriting a buried opening
  10. Prose objections reviewers raise, with the fix
  11. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jom-writing-style skill do?

Use when drafting or polishing prose for a Journal of Operations Management (JOM) empirical manuscript — front-loading the operations argument, writing for both academics and practitioners, keeping APA house style, and meeting JOM's length, formatting, and text-overlap rules.

How do I install it?

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