From jom-skills
Drafts and polishes prose for JOM empirical manuscripts, front-loading the operations argument, writing for academics and practitioners, and enforcing APA style, length, and text-overlap rules.
How this skill is triggered — by the user, by Claude, or both
Slash command
/jom-skills:jom-writing-styleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Prose is jargon-heavy, passive, or buries 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.
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 it matters.
JOM screens with iThenticate/CrossCheck and applies stricter rules than a single global threshold: no single source should account for more than ~1% of wording (outside quotations), and an overall similarity score above 15% must be justified in the cover letter. Paraphrase your own prior work and others' text; do not recycle method or literature paragraphs verbatim.
JOM's dual academic-and-practitioner audience shapes what reads well. The contrasts below are practical orientation; confirm length and similarity specifics against the current Wiley/JOM author guidance.
| Writing dimension | JOM-ready | Stalls with reviewers |
|---|---|---|
| Opening | Operations phenomenon and puzzle on page one | Long literature run-up before the point |
| Voice | Active, concrete operational nouns (fill rate, cycle time) | Passive, nominalized management abstraction |
| Results prose | Statistics translated into operational consequences | Coefficients reported without operational meaning |
| Practitioner relevance | A specific change on the floor or in the network | Relevance asserted but never made concrete |
| Length | Streamlined to ~40 pages | Padded to look comprehensive |
A draft opens with two pages on the resilience literature before naming its question (illustrative). The rewrite leads with the operational puzzle in the first paragraph: "Plants that invested most heavily in redundancy still suffered the longest disruptions — why?" It then states the contribution (redundancy without flexibility delays recovery) before the literature scaffolding, uses active voice, and translates the key estimate into an operational consequence ("each added buffer day shortened recovery by roughly two days only when sourcing was flexible"). A practitioner reads the operational lever immediately; a reviewer sees the operations argument front-loaded. The same content, reordered, moves from academic-only to JOM's dual-audience standard.
【Front-loaded?】operations point in first page ...
【Dual audience】operational consequences stated for practitioners ...
【Length/format】~40 pp, double-spaced 12-pt, APA — compliant? ...
【Similarity risk】single-source <1% / overall <15% or justified ...
【Next step】jom-submission
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin jom-skillsPolishes prose for Management Science (INFORMS) manuscripts — front-loading results, pairing notation with intuition, enforcing author-year citations, and trimming to journal length preferences.
Polishes prose and structure for Journal of Management Studies manuscripts: landing abstracts and intros, sustaining theory-forward narratives, and enforcing Harvard refs, UK/US English, and 200-word abstracts.
Enforces POM manuscript conventions: 32-page cap, author-year citations, practice-relevance style. Use when revising prose to front-load the operations problem and maintain theory-practice balance.