Agent skill · Design & Presentation

ijoc-literature-positioning

Use when staking the computational/methodological contribution of an INFORMS Journal on Computing (IJOC) manuscript against OR/MS and CS prior art. Positions the advance relative to the right baselines and the right frontier; it does not invent citations.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-literature-positioning --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: INFORMS-Journal-on-Computing-Skills/skills/ijoc-literature-positioning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Literature Positioning (ijoc-literature-positioning) ## When to trigger - Reviewers say "the contribution over existing methods is unclear" or "this is incremental" - Your related-work section cites application papers but not the **algorithmic/computational** prior art you actually compete with - You straddle OR and CS literatures and are unsure which frontier you are advancing - A referee names a recent method you did not compare against, and you must decide whether it is the relevant baseline ## Positioning IJOC papers — two frontiers, one claim An IJOC paper usually advances against **two literatures at once**: the OR/MS literature that owns the *problem* and the computing literature that owns the *method*. Your positioning must make clear which frontier you push and by how much, in computational terms. The decisive move is to identify the **state-of-the-art method you must beat or match**, cite it precisely, and commit to it as an experimental baseline. Vague positioning ("little work exists") reads as not having read the field and is a fast path to desk rejection by an Area Editor who knows it well. | Your claim type | The prior art you must engage | The baseline this implie

What's inside
Steps it walks through
  1. When to trigger
  2. Positioning IJOC papers — two frontiers, one claim
  3. Engaging recent work fairly
  4. Sibling-journal framing in the related work
  5. Using the IJOC corpus and deposit as evidence
  6. Checklist
  7. Anti-patterns
  8. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the ijoc-literature-positioning skill do?

Use when staking the computational/methodological contribution of an INFORMS Journal on Computing (IJOC) manuscript against OR/MS and CS prior art. Positions the advance relative to the right baselines and the right frontier; it does not invent citations.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-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.

Keep going