msom-writing-style
Use when polishing the prose of a Manufacturing & Service Operations Management (M&SOM) manuscript — front-loading the operational insight, controlling mathematical notation, writing the structured abstract, and applying INFORMS author-year house style within the 32-page typeset cap. Late-stage polish; do not invoke before the model/identification is settled.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill msom-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Writing Style (msom-writing-style) ## When to trigger - The introduction buries the operational insight under notation or literature - The structured abstract is missing a required part or is jargon-heavy - Notation is dense, inconsistent, or front-loaded before motivation - You are reconciling the manuscript to INFORMS author-year style and the page cap ## Lead with the operations insight, not the math M&SOM readers are operations researchers, but the journal prizes **clarity** and **managerial relevance** alongside technical validity. Open by stating the **operational problem, the decision, and the insight** in words before equations. Introduce notation only when it is needed; a reader should grasp the contribution from the introduction without parsing a model. For analytical papers, narrate the *structure* of the result ("the optimal policy is a threshold that…") rather than dumping the theorem first. ## Write the mandatory structured abstract The abstract is **structured, ≤ 300 words, and free of technical jargon**, with three required subsections: **Problem definition**, **Methodology-results**, and **Managerial implications**. Draft each as one or two plain sentences. The M
- When to trigger
- Lead with the operations insight, not the math
- Write the mandatory structured abstract
- Control notation and structure
- House style and the page cap
- Checklist
- Anti-patterns
- Prose moves that pass M&SOM's clarity bar
- Worked micro-example (illustrative)
- Referee-pushback patterns and the venue fix
- Output format
What does the msom-writing-style skill do?
Use when polishing the prose of a Manufacturing & Service Operations Management (M&SOM) manuscript — front-loading the operational insight, controlling mathematical notation, writing the structured abstract, and applying INFORMS author-year house style within the 32-page typeset cap. Late-stage polish; do not invoke before the model/identification is settled.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill msom-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.