ors-writing-style
Use when polishing the prose and notation of an Operations Research (OR) manuscript — enforcing the equation-free introduction, the text-only abstract under 200 words, clean theorem-proof exposition, and INFORMS author-year house style. Polishes language and house style; it does not formulate the model (ors-theory-development) or run the submission preflight (ors-submission).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-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 & House Style (ors-writing-style) ## When to trigger - Drafts are complete and you want them to read like an *Operations Research* paper. - The introduction contains equations, or the abstract is over 200 words or full of symbols. - You need consistent notation, theorem exposition, and author-year citations. ## OR's distinctive style rules - **Equation-free introduction (hard rule):** the introduction must clearly state the **problem, the results, and their significance to the OR community** and must **contain no equations or mathematical notation**. Write each result as "we show that ..." in plain language. This is a distinctive OR accessibility requirement. - **Abstract:** must **not exceed 200 words** and should be **text-only** — minimize math symbols and avoid accented variables. State the problem, approach, and headline result in prose. - **Keywords:** up to **three**. - **Citations:** **author-year** style, e.g., "(Norman 1977)" or "Norman (1977)". Keep the reference list in the INFORMS author-year convention. ## Theorem-proof exposition - Lead each formal result with a one-sentence plain-language statement of what it means before the symbols. - Keep the **ma
- When to trigger
- OR's distinctive style rules
- Theorem-proof exposition
- Format and clarity
- Prose pushback patterns OR referees raise (with the fix)
- Equation-free rewrite micro-example (illustrative)
- Self-audit before handing to ors-submission
- Anti-patterns
- Output format
What does the ors-writing-style skill do?
Use when polishing the prose and notation of an Operations Research (OR) manuscript — enforcing the equation-free introduction, the text-only abstract under 200 words, clean theorem-proof exposition, and INFORMS author-year house style. Polishes language and house style; it does not formulate the model (ors-theory-development) or run the submission preflight (ors-submission).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-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.