Agent skill · Data & Analytics

mgsci-methods

Use when choosing and defending the method for a Management Science (INFORMS) manuscript — selecting an analytical modeling approach (optimization, stochastic, game/economic theory) or an empirical design (econometric identification, lab/field experiment, structural, data science) that matches the question and the Department's standards. It designs; it does not execute the analysis (mgsci-data-analysis).

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-methods --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: Management-Science-Skills/skills/mgsci-methods/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Methods & Design (mgsci-methods) ## When to trigger - The method may not match the question (wrong model class, weak identification) - You must choose between an analytical model and an empirical study — or combine them - A Department Editor or reviewer will probe whether the design can actually support the claim - You need to pick the field-appropriate standard for your Department lane Management Science has **no single dominant method by design**. Each **Department** sets its own field-appropriate expectations. Pick the lane the question demands, then meet that lane's rigor bar. ## Analytical-modeling design | Question / claim | Approach | |----------------------------------------------------|----------------------------------------------------------| | Optimal policy under constraints | Mathematical programming / optimization (LP/MIP/convex) | | Dynamics, queues, inventory, uncertainty | Stochastic processes, MDPs, dynamic programming | | Strategic interaction among decision-makers | Game theory / mechanism design; state the equilibrium concept | | Pricing/incentives under information frictions | Economic-theory model; contracts, signaling, screening | | Intractable models / p

What's inside
Steps it walks through
  1. When to trigger
  2. Analytical-modeling design
  3. Empirical design
  4. The unifying rigor + relevance bar
  5. Reproducibility is designed in, not bolted on
  6. Department-fit map: which lane bar applies
  7. Worked micro-example (illustrative): designing an operations field experiment
  8. Referee-pushback patterns and the venue-specific fix
  9. Calibration anchors
  10. Execution bridge (StatsPAI / Stata MCP)
  11. Anti-patterns
  12. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the mgsci-methods skill do?

Use when choosing and defending the method for a Management Science (INFORMS) manuscript — selecting an analytical modeling approach (optimization, stochastic, game/economic theory) or an empirical design (econometric identification, lab/field experiment, structural, data science) that matches the question and the Department's standards. It designs; it does not execute the analysis (mgsci-data-analysis).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-methods --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going