Individual skill
ijoc-theory-development
Use when the algorithm or model formulation, its correctness, and its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript. Pins down formulation, complexity, and what the method provably does before experiments are finalized; it does not run the experiments.
INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- 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,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,864 bytes
Read excerpt
# Algorithm & Model Formulation (ijoc-theory-development)
## When to trigger
- An algorithm "works" empirically but its **statement, invariants, and termination** are not written down rigorously
- A formulation is proposed but its **validity** (the model exactly captures the problem; the cuts are valid; the relaxation is correct) is asserted, not argued
- A referee asks for **complexity, convergence, approximation ratio, or correctness** and the paper has none
- A heuristic or ML method needs the **theoretical scaffolding** (what it guarantees, when it can fail) that distinguishes IJOC from a pure benchmark paper
## What "theory" means at IJOC
IJOC is not a pure-theory journal, but it expects the **method to be defined and defended**, not just demonstrated. The advance is computational, yet referees want to know *why the method is correct* and *what it provably achieves* before they trust the experiments. Match the rigor to the archetype — an exact method needs validity and finiteness; a heuristic needs a clear procedure and, where possible, bounds; an ML-for-OR method needs a stated learning task and a guarantee or a falsifiable claim. The theory and the experiments must agree: a proven worst case should be visible in the runtime-vs-size plot.
## Branch paths