Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Jom Literature Positioning

ASecurity

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.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jom Literature Positioning?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Jom Literature Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jom-literature-positioning/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jom-literature-positioning)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: jom-literature-positioning
description: 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.
---

# 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 contribution is **empirical and observed**, not a modeling result. Where prior analytical OM work makes assumptions or predictions, your value is often to *test* them against field/archival/survey/experimental data — "it is the observation that renders the research empirical." Cite the relevant M&SOM / Management Science / Operations Research / Production and Operations Management work, but frame your move as bringing observation to a claim the field has mostly modeled or assumed.

## Align with the Department mission

JOM routes to **12 Departments**, each with its own mission statement (e.g., Healthcare Operations, Sustainable Operations, Inter-organizational Operations, Intervention Based Research, Technology Management). Read your preferred Department's mission and engage the literature it foregrounds; positioning that ignores the Department's conversation reads as misrouted. The Empirical Research Methods Department additionally expects methodological self-awareness in how you situate the design.

## Map the conversation

1. **Anchor works** the field treats as canonical for this phenomenon.
2. **The tension** — competing findings, an unexamined boundary condition, a practice that defies current theory.
3. **Your wedge** — the specific empirical move that resolves or reframes the tension.
4. **Adjacent fields** — borrow from OB, economics, marketing, or IS only to serve the OM argument.

## Anti-patterns

- Citation dumps with no argumentative thread.
- Positioning against analytical OM as if your paper were itself a model.
- Ignoring the target Department's literature.
- Claiming novelty without naming what the field currently believes.

## Output format

```
【Conversation】the OM/SCM debate this enters ...
【Assumption problematized】...
【Empirical wedge vs. analytical priors】...
【Department alignment】preferred Department + its conversation ...
【Anchor + tension + adjacent】...
【Next step】jom-methods
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →