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

Mgsci Writing Style

ASecurity

Use when polishing the prose of a Management Science (INFORMS) manuscript — front-loading the result, keeping notation lean, writing for a cross-department reader, and conforming to author-year citation house style and the journal's preference for short, focused papers. It polishes prose and style; it does not frame the contribution (mgsci-contribution-framing) or build exhibits (mgsci-tables-figures).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill mgsci-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mgsci Writing Style?

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

Security grade badge for Mgsci Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-mgsci-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-mgsci-writing-style)

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

Download with Pro
Files
SKILL.md
---
name: mgsci-writing-style
description: Use when polishing the prose of a Management Science (INFORMS) manuscript — front-loading the result, keeping notation lean, writing for a cross-department reader, and conforming to author-year citation house style and the journal's preference for short, focused papers. It polishes prose and style; it does not frame the contribution (mgsci-contribution-framing) or build exhibits (mgsci-tables-figures).
---

# Writing Style (mgsci-writing-style)

## When to trigger

- The prose is notation-dense, passive, or buries the main result
- An analytical paper reads as a symbol dump with no verbal intuition
- The writing assumes a reader already inside your sub-niche
- You are over length and the text is padded

Management Science explicitly **prefers short, focused papers** and warns that excessive length and **notation density slow review**. The style bar is rigor expressed economically and read by editors across many departments.

## Front-load the result

State what you find and why it matters in the abstract and the first pages. A Department Editor desk-screening dozens of papers should see the result, the mechanism, and the decision relevance early — not after twenty pages of setup. The abstract is **250 words or less** with **3–5 keywords**; make every word carry the contribution.

## Pair every symbol with intuition (analytical lane)

Formal rigor is required, but a Management Science paper is not a proof transcript. For each key model object and result, give the **plain-language reading**: what the assumption means behaviorally, what the proposition says in words, what the comparative static implies for a decision-maker. Introduce notation only when used, keep it minimal and consistent, and never make the reader hold five symbols in their head to follow a sentence.

## Write for a cross-department reader

Because the contribution must **travel across departments**, avoid sub-field jargon that only your immediate stream parses, or define it on first use. A finance reader should follow your operations result's significance, and vice versa. This breadth of audience is a defining feature of the flagship, not an optional courtesy.

## Citation and format house style

- **Author-year (name–date)** in-text citations, e.g., (Norman 1977) or Norman (1977); alphabetical reference list in INFORMS/journal style.
- Manuscripts double- or 1.5-spaced, **11-pt font, 1-inch margins**; PDF preferred for submission.
- Keep prose active and direct; cut throat-clearing and redundant restatement.

## Length discipline

There is no formal limit at initial submission, but brevity is rewarded and **invited revisions** are capped (47 pages double-spaced / 32 pages 1.5-spaced, online appendix excluded). Tighten now so a revision is not a triage emergency later.

## Anti-patterns

- A first page that is all background and no result.
- Symbols introduced pages before they are used, or never verbally interpreted.
- Jargon that only your sub-niche understands, in a cross-department venue.
- Numbered-citation style instead of author-year.

## Output format

```
【Front-loaded?】result + decision relevance in abstract/first pages: yes/no
【Notation ↔ intuition】every key result interpreted in words: yes/no
【Cross-department readability】jargon defined / minimized: yes/no
【House style】author-year; 11-pt, 1-inch; abstract ≤250 words, 3–5 keywords: yes/no
【Length】tight; revision cap reachable: yes/no
【Next step】mgsci-submission
```

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 →