ors-contribution-framing
Use when articulating the contribution of an Operations Research (OR) manuscript — especially the mandatory cover-letter contribution statement (since 1 June 2023, fewer than 500 words) and the discussion's significance claims. Frames why the work matters to OR; it does not position against specific prior papers (ors-literature-positioning) or run experiments (ors-data-analysis).
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-contribution-framing --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.
# Contribution Framing (ors-contribution-framing) ## When to trigger - You must write the **mandatory contribution statement** for the cover letter. - The introduction and discussion need to state significance to the OR community. - A reviewer says "the contribution is incremental" or "significance to OR is unclear." ## The mandatory contribution statement (OR-specific) Since **1 June 2023**, *Operations Research* requires the cover letter to include a statement, in **fewer than 500 words**, articulating the manuscript's **novel, innovative, and rigorous original contribution to operations research**. Treat this as a first-class deliverable, not boilerplate. A strong statement: - Names the **methodological contribution** in one or two sentences a non-specialist OR reader can grasp (new model class, first provable guarantee, tighter bound/rate, algorithm with better complexity, new analysis technique). - Says **what was not possible before** and is now — the precise delta over prior art. - Establishes **rigor**: which results are theorems/propositions and what they guarantee; that computation/simulation is reproducible. - States **significance**: which OR problems, methods, or appli
- When to trigger
- The mandatory contribution statement (OR-specific)
- Frame the three pillars: novel · innovative · rigorous
- Carry significance into the paper
- What OR area editors weigh in the contribution statement
- Contribution pushback patterns and the fix
- Worked statement skeleton (illustrative)
- Anti-patterns
- Output format
What does the ors-contribution-framing skill do?
Use when articulating the contribution of an Operations Research (OR) manuscript — especially the mandatory cover-letter contribution statement (since 1 June 2023, fewer than 500 words) and the discussion's significance claims. Frames why the work matters to OR; it does not position against specific prior papers (ors-literature-positioning) or run experiments (ors-data-analysis).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ors-contribution-framing --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.