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 Data Analysis

ASecurity

Use when executing and reporting the analysis for a Manufacturing & Service Operations Management (M&SOM) manuscript — proving structural results and running numerical studies for analytical work, or estimating and stress-testing identified effects for empirical work, plus meeting M&SOM's data-and-code replicability policy. Executes the analysis designed in msom-methods.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Msom Data Analysis?

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

Security grade badge for Msom Data Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-msom-data-analysis/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-msom-data-analysis)

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

Download with Pro
Files
SKILL.md
---
name: msom-data-analysis
description: Use when executing and reporting the analysis for a Manufacturing & Service Operations Management (M&SOM) manuscript — proving structural results and running numerical studies for analytical work, or estimating and stress-testing identified effects for empirical work, plus meeting M&SOM's data-and-code replicability policy. Executes the analysis designed in msom-methods.
---

# Analysis & Replicability (msom-data-analysis)

## When to trigger

- Proofs are drafted and you need a numerical study that earns its keep
- Estimates exist and you must defend identification and robustness
- A reviewer says "the result is an artifact of the assumptions/specification"
- You are preparing the data and code disclosure M&SOM requires

## Analytical work: proofs plus a disciplined numerical study

M&SOM's dominant tradition is **analytical/stochastic modeling**, so rigor is judged first on the **proofs** and then on a numerical study that does real work:

- **Proofs**: state results as propositions/theorems; full proofs go in the online supplement (≤ 16 pages for a new submission). Verify monotonicity/convexity/threshold or base-stock structure rigorously.
- **Numerical study**: use realistic parameter ranges; quantify the *magnitude* of the structural effect, the value of the proposed policy versus benchmarks/heuristics, and the cost of relaxed assumptions. Report instance generation, seeds, and solver/settings so results reproduce.
- **Sensitivity**: show which assumptions bind and how conclusions move as primitives (demand variability, lead time, cost ratios) change.

## Empirical work: identified effects, not correlations

- Defend the **identification** designed in `msom-methods`: parallel-trends/event-study evidence for DiD, first-stage strength and exclusion for IV, density/covariate-balance for RDD, model fit and identification for structural estimation.
- Treat operational decisions (capacity, inventory, staffing, routing) as **endogenous**; address selection and simultaneity explicitly.
- **Robustness**: alternative specifications, samples, and operational measures; cluster standard errors at the operational unit; report effect *magnitudes* in operational terms (units, hours, dollars), not just significance.

## Replicability policy (M&SOM / INFORMS)

Manuscripts must contain enough detail and references to **permit replication**. You may be asked to provide raw data for editorial review, must be prepared to share it, and must **retain it** for a reasonable time after publication. For **licensed data** (Census, Compustat, CRSP, FactSet, WRDS) provide your **own code plus detailed access/linking instructions** so others can replicate without your redistributing the data. Any reuse of shared data/code beyond replicability verification must **cite the paper and acknowledge the source**.

## Checklist

- [ ] Analytical: results stated as propositions; full proofs in the ≤16-page supplement
- [ ] Numerical study with realistic ranges; magnitudes vs. benchmarks; seeds/settings reported
- [ ] Empirical: identification defended (trends/first-stage/balance); endogeneity addressed
- [ ] Robustness across specifications/samples/measures; SEs clustered at the operational unit
- [ ] Effects reported in operational magnitudes, not p-values alone
- [ ] Data/code disclosure prepared; licensed-data access instructions included; retention noted

## Anti-patterns

- "Numerical results show…" with no benchmark comparison or assumption stress-test.
- Proofs in the main text crowding out the operational insight (move them to the supplement).
- Treating capacity/inventory/staffing as exogenous in an empirical design.
- Reporting significance with no operational magnitude.
- Promising replication while withholding code/access instructions for licensed data.

## Output format

```
【Analytical】propositions proven; supplement proofs: yes/no
【Numerical study】ranges / benchmarks / magnitude / seeds ...
【Empirical identification】trends / first-stage / balance ...
【Robustness】specs / samples / measures; SE clustering ...
【Replicability】data+code disclosure; licensed-data access instructions ...
【Next step】msom-contribution-framing
```

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 →