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

Msom Literature Positioning

ASecurity

Use when positioning a Manufacturing & Service Operations Management (M&SOM) manuscript within the operations-management literature — engaging the canonical OM streams (inventory, queueing, supply-chain contracting, revenue management, service operations, empirical OM), selecting the target editorial Department, and stating the operational conversation the paper joins.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Msom Literature Positioning?

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

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

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

Download with Pro
Files
SKILL.md
---
name: msom-literature-positioning
description: Use when positioning a Manufacturing & Service Operations Management (M&SOM) manuscript within the operations-management literature — engaging the canonical OM streams (inventory, queueing, supply-chain contracting, revenue management, service operations, empirical OM), selecting the target editorial Department, and stating the operational conversation the paper joins.
---

# Literature Positioning (msom-literature-positioning)

## When to trigger

- Your front end reads as "no one has studied X" rather than joining an OM conversation
- A reviewer says the relevant operations stream is not engaged
- You are unsure which of the six Departments the related work points to
- You need to distinguish your contribution from close OM antecedents

## Join an operations conversation, not a generic gap

M&SOM positions itself as the **premier journal for the operations management research community**. Position the paper inside the established OM streams it speaks to — e.g., inventory/supply-chain (newsvendor, base-stock, contracting and coordination), queueing and service operations, revenue management and pricing, platforms and matching, sustainable/healthcare operations, or empirical/data-driven OM. State the **operational conversation** you join and what you change in it, rather than claiming a void.

## Let the citations point to a Department

The literature you engage should make your **target Department** obvious to an editor — Manufacturing & Supply Chain Operations; Services, Platforms & Revenue Management; Environment, Health & Society; Operational Innovation; Analytics in OM; or the Practice Platform. Scattering across departments signals an unfocused contribution. Cite the foundational results your model or estimation builds on (the policy structures, the contracting benchmarks, the identification strategies) so reviewers see you stand on the right shoulders.

## Distinguish from close antecedents on the operational lever

Differentiate not by "different data" but by the **operational decision or mechanism** you newly capture: a richer model primitive, a relaxed assumption that changes the optimal policy form, a previously untested operational channel, or a credibly identified effect a prior analytical paper only conjectured. Analytical-vs-empirical complementarity is a strong position: empirically testing a structural prediction, or analytically explaining an empirical regularity.

## Checklist

- [ ] Two to four canonical OM streams explicitly engaged
- [ ] Target Department evident from the citation pattern
- [ ] Foundational results your contribution builds on are cited
- [ ] Differentiation stated in terms of the operational lever/mechanism, not just setting
- [ ] Contribution framed as joining/advancing a conversation, not filling a void

## Anti-patterns

- "No prior work has examined…" gap-spotting with no engaged OM stream.
- Citing across all six departments so the fit is ambiguous.
- Differentiating only by dataset or industry, not by the operations mechanism.
- Ignoring the closest analytical or empirical antecedent because it is inconvenient.

## Output format

```
【OM streams engaged】...
【Implied Department】...
【Foundational works cited】...
【Differentiation】operational lever/mechanism that is new ...
【Conversation joined】...
【Next step】msom-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 →