Agent skill

jom-literature-positioning

Use when positioning a Journal of Operations Management (JOM) manuscript within the operations and supply chain management conversation — joining a live OM/SCM debate, distinguishing the paper from analytical OM work, and aligning the framing with the target Department's mission.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-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: 6 KB
Bundled scripts: none
Path: Journal-of-Operations-Management-Skills/skills/jom-literature-positioning/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +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 for JOM (jom-literature-positioning) ## When to trigger - Your introduction lists prior studies instead of joining a debate - A reviewer says "what conversation is this paper in?" or "how is this different from existing OM work?" - Your citations skew toward analytical/optimization OM but your study is empirical (or vice versa) - You are unsure which OM/SCM literature the chosen Department expects you to engage ## Join an OM/SCM conversation, don't spot a gap A bare "no one has studied X" is weak. Position the paper as a contribution to an ongoing **operations and supply chain management** conversation: what does the field currently believe about this operational phenomenon, what tension or anomaly does your evidence expose, and how does resolving it move the OM conversation forward? Problematize a shared assumption (e.g., that more buffering always helps, that lean and resilience trade off cleanly, that automation uniformly reduces errors) rather than merely noting an empty cell. ## Distinguish from analytical OM explicitly Because JOM does **not** publish purely analytical models or optimization techniques, your positioning should make clear that the cont

What's inside
Steps it walks through
  1. When to trigger
  2. Join an OM/SCM conversation, don't spot a gap
  3. Distinguish from analytical OM explicitly
  4. Align with the Department mission
  5. Map the conversation
  6. Anti-patterns
  7. How JOM referees read the front end
  8. Desk-reject and return triggers on positioning
  9. Worked vignette: positioning a behavioral-OM ordering study
  10. Positioning objections and the corrective move
  11. Calibrating against the empirical-OM identity (hedged)
  12. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jom-literature-positioning skill do?

Use when positioning a Journal of Operations Management (JOM) manuscript within the operations and supply chain management conversation — joining a live OM/SCM debate, distinguishing the paper from analytical OM work, and aligning the framing with the target Department's mission.

How do I install it?

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