From msom-skills
Polishes M&SOM manuscripts: front-loads operational insight, controls notation, writes structured abstract, applies INFORMS author-year style within 32-page cap.
How this skill is triggered — by the user, by Claude, or both
Slash command
/msom-skills:msom-writing-styleThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The introduction buries the operational insight under notation or literature
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.
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 Managerial-implications subsection is required — never drop it or fill it with notation.
Use INFORMS author-year (author-date) in-text citations with cited pages where appropriate; order the reference list by first author, number of authors, then year (INFORMS style file v1.6). Write inside the official template — the 32-page cap includes references, tables, figures, and appendices, so tighten prose and push overflow to the supplement rather than shrinking margins or fonts (the template fixes 11-pt, one column, 1-inch margins).
M&SOM weights clarity and managerial relevance alongside validity, so the prose is graded. Narrate the policy form before the theorem; defer notation rather than dumping symbols up front; turn a closing "implications for managers" nod into a specific decision rule; write the abstract in the required structured subsections; and beat the page cap by cutting prose, never by shrinking the template. The test: a competent operations practitioner should grasp the decision, the insight, and the managerial takeaway without parsing a single equation.
Vignette: an analytical paper on dynamic capacity allocation for a cloud-computing provider. A theorem-first opening reads "Proposition 1 establishes the value function is concave and the optimal admission policy monotone." The M&SOM rewrite leads with the insight in words: "When demand is volatile, reserve capacity for high-value jobs up to a threshold that tightens as volatility rises." The managerial-implications subsection then carries one plain sentence with an illustrative magnitude — thresholding lifts revenue per server-hour by roughly 8% over first-come-first-served. Same result; the operations insight now leads.
【Intro】operational insight stated before notation? ...
【Structured abstract】three required sections present; ≤300 words; jargon-free ...
【Notation】defined / minimal / consistent ...
【Proofs】in ≤16-page supplement; intuition in body ...
【Style & cap】INFORMS author-year; within 32 typeset pages ...
【Next step】msom-submission
npx claudepluginhub brycewang-stanford/awesome-journal-skills --plugin msom-skillsPolishes prose for Management Science (INFORMS) manuscripts — front-loading results, pairing notation with intuition, enforcing author-year citations, and trimming to journal length preferences.
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.
Polishes Marketing Science manuscripts: front-loads model intuition before notation, manages formal apparatus for readability, enforces INFORMS author-year formatting. For late-stage revision.