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).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-literature-positioning --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.
# 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. ## Map the neighborhood precisely - **Identify the closest 3-5 papers**, not a wall of citations. For each, record: the model class and assumptions, the strongest result, the algorithm and its complexity/convergence, and the regime where it applies. - **State your delta against each** in concrete terms: weaker assumptions, a tighter bound, a better rate or complexity, a broader model class, a new regime (heavy-traffic, high-dimensional, adversarial), or the first provable guarantee. - **Cross-stream placement.** OR problems often si
- When to trigger
- How OR positioning differs
- Map the neighborhood precisely
- Make novelty checkable
- Author-year citation convention
- Positioning pushback patterns and the OR-specific fix
- Worked positioning vignette (illustrative numbers)
- Anti-patterns
- Output format
What does the ors-literature-positioning skill do?
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).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-literature-positioning --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.