Individual skill

ijoc-writing-style

Use when the prose, abstract, or introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance or misreads the house voice. Makes the method land for an OR-meets-CS readership; it does not change the underlying results.

INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,409
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Writing Style (ijoc-writing-style)

## When to trigger

- The abstract reads like an application summary and never states the computational advance
- The introduction takes pages to reach "what is new computationally"
- The method section is unreadable prose where pseudocode and structured statements belong
- The paper is over the **25-page limit** and needs tightening, not just trimming
- A coauthor wants the draft to read like an IJOC paper, not a CS conference paper or an OR theory paper

## The IJOC voice

IJOC readers are OR/MS researchers comfortable with computation and CS researchers comfortable with OR — write for both. The voice is **precise, methods-forward, and quantitative**: state the problem, state the method, state what it provably and empirically achieves, in that order. Avoid two failure modes the readership notices instantly — the *application-essay* voice that delays the method, and the *CS-conference* voice that drops OR rigor (no problem formulation, no fair baseline discussion). The house format reinforces brevity: single-column, 1.5-spaced, 12-point, 1-inch margins, with a **≤300-word abstract carrying no formulas or mathematical notation** (检索于 2026-06;以官网为准).
Back to top