Correct
cursor/plugins
Find the mistakes agents keep repeating in this repo and make each one impossible.
Agent skill
Ijoc Theory Development
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when the algorithm or model formulation, its correctness, and its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript.
MITAuto-check passed
Install Ijoc Theory Development
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-theory-development --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development .claude/skills/ijoc-theory-development && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ijoc-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development into .claude/skills/ijoc-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-theory-development", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-developmentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-theory-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development .agents/skills/ijoc-theory-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ijoc-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development into .agents/skills/ijoc-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-theory-development", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-theory-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development .cursor/skills/ijoc-theory-development && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ijoc-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development into .cursor/skills/ijoc-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-theory-development", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-theory-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development .gemini/skills/ijoc-theory-development && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ijoc-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development into .gemini/skills/ijoc-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-theory-development", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-theory-developmentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development .github/skills/ijoc-theory-development && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ijoc-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development into .github/skills/ijoc-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-theory-development", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-theory-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development .opencode/skills/ijoc-theory-development && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ijoc-theory-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development into .opencode/skills/ijoc-theory-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-theory-development", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ijoc-theory-development- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 701 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the algorithm or model formulation, its correctness, and its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript.
- Model formulation
- SKILL.md covers When to trigger, What "theory" means at IJOC, Branch paths and Checklist, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Its correctness
What it does
Ijoc Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Model formulation
- Its correctness
- Its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript
Example prompts
- “/ijoc-theory-development”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ijoc Theory Development loads about 1.5k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 701 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 701 words, ~1,456 tokens.
Download SKILL.mdSave it as
.claude/skills/ijoc-theory-development/SKILL.md (or your agent's skills folder).- name
- ijoc-theory-development
- description
- 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.
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
Branch A: Exact methods (B&B / B&C / B&P, decomposition)
- State the formulation precisely and prove it is a valid model of the problem (feasible region = exactly the intended solutions).
- Prove validity of cuts / columns / Benders cuts; show the separation/pricing problem and its complexity.
- Argue finite termination / correctness of the algorithm; state the relaxation and any bound-tightening.
- Complexity: give the per-iteration cost and, where possible, worst-case size; if NP-hard, say so and motivate the empirical study that follows.
Branch B: Heuristics / metaheuristics / matheuristics
- Write the procedure as pseudocode with explicit neighborhood/operators, acceptance rule, and stopping criterion — reproducibility starts here.
- State guarantees where they exist: approximation ratio, performance bound, local-optimality conditions; if none, say the contribution is empirical and design the experiments to earn that claim.
- Argue why the design fits the structure of the problem (what the operator exploits), not just "it performed well."
Branch C: Machine learning for OR / learning-to-optimize
- Define the learning task and the loss precisely; state what is learned and what is solved exactly.
- Generalization claim: state the distribution of instances and what is claimed to transfer; provide a guarantee or a falsifiable out-of-distribution test plan.
- Feasibility/optimality safeguards: if a learned policy can produce infeasible or arbitrarily bad solutions, state the repair/guarantee that prevents it.
Show full SKILL.md (302 more words)Show less
Branch D: Simulation / computational probability
- Specify the model and estimator; state unbiasedness/consistency and the variance behavior.
- Variance reduction: state the technique (CRN, control variates, importance sampling) and prove or argue it reduces variance for this estimand.
- Convergence / error bounds for the computational scheme; state regularity assumptions.
Checklist
- Branch chosen; the method is stated as a formal formulation or pseudocode, not prose only
- Exact: model validity proven; cuts/columns valid; finite termination/correctness argued; complexity stated
- Heuristic: full pseudocode; bounds stated where they exist; design tied to problem structure
- ML-for-OR: learning task + loss defined; generalization claim falsifiable; feasibility safeguard stated
- Simulation: estimator properties + variance-reduction justification given
- Every theorem has assumptions stated and a proof (main text or supplement, but referenced)
- The theoretical claim and the experimental claim do not contradict each other
Anti-patterns
- "The algorithm converged / it works" presented as if it were correctness or a guarantee
- Asserting cut/column validity without proof — a fatal flaw for an exact-methods paper
- A heuristic with no pseudocode, so neither referee nor the GitHub deposit can reproduce it
- An ML-for-OR method that can return infeasible solutions with no stated safeguard
- Claiming an approximation ratio that the experiments quietly violate
- Burying the proof of a key result in a supplement the main paper depends on (keep the main paper self-contained on its central claims)
Worked vignette (illustrative)
A paper proposes new valid inequalities for a stochastic facility-location MIP and a branch-and-cut that uses them. A weak version says "the cuts helped." An IJOC version: state the polyhedral result (the inequalities are facet-defining under a stated condition), give the separation algorithm and its O(n log n) cost, and prove they are valid for the original feasible region. Then the experiments are interpretable — the root-gap closure (say 31%, illustrative) and the node-count reduction are predicted by the theory, not surprises.
Output format
【Branch】exact / heuristic / ML-for-OR / simulation
【Formulation or pseudocode】stated? [Y/N]
【Guarantee】validity / finiteness / complexity / approx ratio / variance — which, and proven where
【Assumptions】[...]
【What it does NOT guarantee】[...]
【Theory–experiment consistency】[Y/N]
【Next skill】ijoc-literature-positioning© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ijoc Theory Development next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ijoc Theory Development this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Correctcursor/plugins | 11k | 3 repos | ~612 | Automated safety check: Pass | None | |
| CorrectionNxcoreAI/EverRoom | 3k | — | ~290 | Automated safety check: Pass | Custom licence | |
| Algorithmic Art with p5.jsanthropics/skills | 180k | 38 repos | ~4.9k | Automated safety check: Pass | Apache-2.0 | |
| AlgorithmSnailclimb/interview-guide | 3.3k | — | ~129 | Automated safety check: Pass | AGPL-3.0 | |
| Statistical Problem Formulationaiming-lab/AutoResearchClaw | 15k | — | ~671 | Automated safety check: Pass | MIT |
Similar skills
- Official
Correction
NxcoreAI/EverRoom
Compute Room overview corrections—citation corrections as per-claim edits and general corrections as a single proposal.
- Official
Algorithmic Art with p5.js
anthropics/skills
Creates original generative art in two steps: a written algorithmic philosophy, then a p5.js sketch with seeded randomness and an interactive viewer for exploring parameters.
Algorithm
Snailclimb/interview-guide
用于算法面试出题；重点评估复杂度分析、边界处理和优化能力，区分背题与真实理解。
Statistical Problem Formulation
aiming-lab/AutoResearchClaw
Formulate statistical research problems with formal notation, target parameters, assumptions, hypotheses, evaluation criteria, and theory targets.
Statistical Theory Analysis
aiming-lab/AutoResearchClaw
Analyze theoretical properties of statistical methods under the formal formulation: identifiability, bias, variance, consistency, asymptotics, coverage, error bounds, robustness, and limitations.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Ijoc Theory Development
What does Ijoc Theory Development do?
A skill your agent uses when the algorithm or model formulation, its correctness, and its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript. Ijoc Theory Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when the algorithm or model formulation, its correctness, and its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript.
When should I use Ijoc Theory Development?
Ijoc Theory Development fits situations like: model formulation; its correctness; its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript.
How do I install Ijoc Theory Development in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a claude-code`. Or copy the skill folder (INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ijoc-theory-development in your project. Claude Code loads it when a task matches its description.
How do I install Ijoc Theory Development in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a codex`. Or copy the skill folder (INFORMS-Journal-on-Computing-Skills/skills/ijoc-theory-development in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ijoc-theory-development in your project. Codex loads it when a task matches its description.
Can I use Ijoc Theory Development in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-theory-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ijoc-theory-development, .gemini/skills/ijoc-theory-development, .github/skills/ijoc-theory-development and .opencode/skills/ijoc-theory-development in your project.
What does Ijoc Theory Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Ijoc Theory Development is instructions for the agent only.
Does Ijoc Theory Development access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ijoc Theory Development safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ijoc Theory Development use?
Ijoc Theory Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ijoc Theory Development use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ijoc Theory Development?
Skills that share tags, products or a category with Ijoc Theory Development: Correct (cursor/plugins, 11k stars), Correction (NxcoreAI/EverRoom, 3k stars), Algorithmic Art with p5.js (anthropics/skills, 180k stars) and Algorithm (Snailclimb/interview-guide, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ijoc Theory Development?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.