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 Topic Selection

ASecurity

Use when shaping or stress-testing a research question for Manufacturing & Service Operations Management (M&SOM) — confirming an operations decision is central, choosing the analytical-vs-empirical lane, and matching the question to the right editorial Department before any modeling or data work begins.

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

Works with

api

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Msom Topic Selection?

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

Security grade badge for Msom Topic Selection
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-msom-topic-selection/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-msom-topic-selection)

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

Download with Pro
Files
SKILL.md
---
name: msom-topic-selection
description: Use when shaping or stress-testing a research question for Manufacturing & Service Operations Management (M&SOM) — confirming an operations decision is central, choosing the analytical-vs-empirical lane, and matching the question to the right editorial Department before any modeling or data work begins.
---

# Topic Selection & M&SOM Fit (msom-topic-selection)

## When to trigger

- You have a problem idea but are unsure it belongs in M&SOM versus a general OR or strategy venue
- A senior co-author asks "where is the operations decision here?"
- You must pick which of the six editorial Departments your work targets
- You are deciding whether to pursue this as an analytical model or an empirical study

## The operations-centrality gate

M&SOM's defining screen is that an **operations decision or problem is central to the contribution**, not a backdrop. The journal covers the **design, procurement, production, delivery, and recovery of goods and services**. A strong analytics, pricing, marketing, or finance paper that merely *uses* an operational setting is routinely desk-screened. Before anything else, write one sentence: *"The operational decision is ___, the tradeoff is ___, and the operational lever is ___."* If you cannot, the topic is not yet M&SOM-ready.

## Choose the lane (and the journal will route by it)

M&SOM publishes **both** analytical/stochastic modeling (optimization, queueing, stochastic models, game theory, revenue management) **and** empirical OM / data-driven analytics. Pick the lane that the *decision* demands:

- **Analytical** when the contribution is a tractable model yielding structural insight about an operational policy (e.g., base-stock structure, threshold pricing, equilibrium contract).
- **Empirical** when the contribution is a credibly identified operational effect or a data-driven policy validated on real operations.

## Match to a Department (this is fit)

Map the question to one of the six departments — Manufacturing & Supply Chain Operations; Services, Platforms & Revenue Management; Environment, Health & Society; Operational Innovation; Analytics in OM; or the Practice Platform. A field-driven or practice-based study may target the Practice Platform; a thought-leadership perspective is an **OM Forum** piece (an identifying banner), not a standard research article. Your topic should clearly belong to one department, because the manuscript's fate hinges on that match.

## Checklist

- [ ] One-sentence operational decision / tradeoff / lever written
- [ ] Analytical vs. empirical lane chosen for principled reasons
- [ ] Target Department identified (and a sensible second choice)
- [ ] Managerial/operational "so what" stated in plain language
- [ ] Confirmed the OM core is the *primary* contribution, not an application backdrop

## Anti-patterns

- A pricing/finance/ML paper dressed in operations vocabulary with no real operational lever.
- "We apply method X to an operations dataset" with no operations decision improved.
- Targeting M&SOM generically without picking a department.

## Output format

```
【Operations decision】lever / tradeoff ...
【Lane】analytical / empirical — why ...
【Department】primary + second choice ...
【So-what】managerial implication ...
【Verdict】M&SOM-fit: yes / reshape / wrong venue
【Next step】msom-theory-development
```

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 →