Individual skill
ors-literature-positioning
Use when placing an Operations Research (OR) manuscript against the OR/MS literature — separating your model, results, and algorithmic guarantees from the closest prior work so the novelty is unambiguous. Positions the contribution; it does not formulate the model (ors-theory-development) or write the contribution statement (ors-contribution-framing).
Operations-Research-Skills/skills/ors-literature-positioning/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- 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.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- research Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,468 bytes
Read excerpt
# Literature Positioning (ors-literature-positioning)
## When to trigger
- Reviewers will ask "how is this different from [closest paper]?"
- Multiple streams (optimization, stochastic, learning) touch your problem and you must situate it.
- You need to show your bound/rate/model strictly improves or genuinely differs from prior art.
## How OR positioning differs
In *Operations Research*, positioning is **technical**, not rhetorical. The reader
must see exactly which model assumptions, result strengths, or algorithmic guarantees
you change relative to the nearest prior work. Vague "gap" language does not satisfy
OR reviewers — they want a precise delta.