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

Management Science

ASecurity

Use when targeting Management Science (MS) or deciding whether an operations / finance / information-systems / marketing / decision-analysis / behavioral / strategy manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.

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 management-science --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Management Science?

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

Security grade badge for Management Science
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-management-science/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-management-science)

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

Download with Pro
Files
SKILL.md
---
name: management-science
description: Use when targeting Management Science (MS) or deciding whether an operations / finance / information-systems / marketing / decision-analysis / behavioral / strategy manuscript fits this venue. Encodes the journal's fit, framing, method-and-evidence bar, house style, official-submission re-check, and desk-reject heuristics.
---

# Management Science (management-science)

## Journal positioning

Management Science is INFORMS's flagship umbrella journal and one of the most cited business journals across the entire management spectrum. It is unusual in that it is not a single-subfield outlet: it is organized into many departments — operations management, optimization, stochastic models, finance, accounting, information systems, marketing, decision analysis, behavioral economics, entrepreneurship/innovation, strategy, organizations, healthcare, and more — each run by a department editor (DE) who owns the standards for that area. A paper succeeds when it clears the uniformly high rigor bar of the *right department*, whether it is a clean analytical model or a clean empirical study. The readership is the broad quantitative management community, so a paper must matter beyond its niche and be legible to scholars who are not specialists in its method.

This skill is a **fit / venue-selection / re-framing** tool. It does not replace the journal's current official submission guidelines. Before submitting, re-check the live author instructions on the INFORMS / Management Science site and the editorial submission system.

## When to trigger

- The author names Management Science / MS (or the INFORMS / FT50 / UTD24 quantitative-management elite) as the target venue.
- A rigorous analytical-modeling or empirical paper spans subfields and the author must decide which department to submit to.
- A general operations, finance, IS, marketing, or decision paper needs re-framing into a contribution that one MS department will own.
- The author needs MS's desk-reject risks and a credible field-flagship alternative list before submitting.

## Scope & topic fit

- Analytical / modeling work: optimization, stochastic models, game-theoretic and mechanism-design models of operations, pricing, contracting, finance, and information economics — with a clear managerial or economic insight, not math for its own sake.
- Rigorous empirics: causal-inference field studies, structural estimation, lab and field experiments, and large-scale data work across operations, finance, IS, marketing, and behavioral domains.
- Decision analysis, behavioral operations/economics, judgment under uncertainty, and prescriptive analytics.
- Topics that fit a named department; submitting to the wrong department is the single most common avoidable error.

## Method & evidence bar

- Uniformly high rigor regardless of department: analytical papers need correct, non-trivial results with proofs (typically in an appendix) and a managerial takeaway; empirical papers need credible identification or a defensible structural model.
- The contribution must be generalizable insight, not a one-context application; a model's assumptions and an empirical design's exclusion restrictions must be defended.
- Empirical causal claims meet current standards (DiD/IV/RDD/experiments, proper inference, robustness, placebo/falsification).
- Behavioral work needs adequate power, pre-registration where the department expects it, and replicable designs.

## Structure & house style

- The introduction states the management problem, the modeling or empirical approach, and the general insight early; it must read to a non-specialist quantitative audience.
- Choose and signal the target department; frame the contribution in that department's language and against that department's recent MS papers.
- Proofs, extended derivations, robustness, and secondary analyses go to an electronic companion / online appendix.
- Exhibits report economic or managerial magnitudes and interpret them, not just significance or existence.

## Official-submission checklist

- Before giving submission-ready advice, read `../../resources/source-basis.md` and `../../resources/official-source-map.md`; start from the official source anchors for this journal family, then cite the current journal-specific page you checked.
- Search the live site for "Management Science submission guidelines / author instructions" and follow the current INFORMS version, including the list of departments and their stated scope.
- Re-check the current department list and DE assignments, formatting, abstract length, anonymization/double-blind policy, and reference style.
- Re-check the current data and code availability / reproducibility policy, electronic-companion rules, and disclosure/ethics requirements.
- If the live official instructions conflict with this skill, the official instructions win.

## Pre-submission self-check

- [ ] One sentence stating the general management insight, legible to a non-specialist.
- [ ] The correct target department is identified and the framing matches it.
- [ ] The contribution is stated as a model result / identification / mechanism, not as statistical significance.
- [ ] Proofs or identification arguments are complete; robustness lives in the electronic companion.
- [ ] Abstract, anonymization, references, and data/code policy match the current MS guide.

## Common desk-reject triggers

- Submitting to the wrong department, or a paper too narrow for any department's general-insight bar.
- An analytical model with a correct but managerially uninteresting result, or unrealistic assumptions with no defense.
- An empirical paper with significant coefficients but no identification or mechanism.
- A method/algorithm paper with no managerial payoff (often belongs at an INFORMS computing or OR venue).

## Re-routing decision

- OR methodology, optimization, queueing, stochastic theory → `operations-research`; computational/algorithmic OR or ML-for-OR → `informs-journal-on-computing`.
- OM theory/models or empirical OM → `manufacturing-and-service-operations-management`, `production-and-operations-management`, or `journal-of-operations-management`.
- IS-core contribution → `mis-quarterly`, `information-systems-research`, `journal-of-management-information-systems`, or `journal-of-the-association-for-information-systems`.
- Finance-core → the finance top-3 (`journal-of-finance`, `journal-of-financial-economics`, `review-of-financial-studies`); management-theory-core → `academy-of-management-journal`.

## Output format

```text
[Fit] High / Medium / Low (one-line reason)
[Target] Management Science
[Topic tags] <2–3 closest topics + target department>
[Method/evidence] <does the model result or identification clear the department's bar?>
[Top risk] <the single most likely reason for rejection>
[Official items to re-check] <department list / submission system / blinding / electronic companion / data-code>
[Re-route suggestion] <if not a fit, a better-matched venue>
```

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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', ...

693161 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.

691 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 →