Individual skill

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).

Operations-Research-Skills/skills/ors-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top