Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when the prose, abstract, or introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance or misreads the house voice.
Install Ijoc Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-writing-style --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-writing-style .claude/skills/ijoc-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style into .claude/skills/ijoc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-writing-style --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-writing-style .agents/skills/ijoc-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style into .agents/skills/ijoc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-writing-style --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-writing-style .cursor/skills/ijoc-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style into .cursor/skills/ijoc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ijoc-writing-style --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-writing-style .gemini/skills/ijoc-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style into .gemini/skills/ijoc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/ijoc-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style into .github/skills/ijoc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/ijoc-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style into .opencode/skills/ijoc-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ijoc-writing-style", 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-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 698 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when the prose, abstract, or introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance or misreads the house voice.
- Introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance
- SKILL.md covers When to trigger, The IJOC voice, The abstract: three moves in… and The introduction: reach the…, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Misreads the house voice
What it does
Ijoc Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Brand voice and tone. 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
- Introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance
- Misreads the house voice
Example prompts
- “/ijoc-writing-style”
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 Writing Style loads about 1.4k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 698 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). 698 words, ~1,407 tokens.
Download SKILL.mdSave it as
.claude/skills/ijoc-writing-style/SKILL.md (or your agent's skills folder).- name
- ijoc-writing-style
- description
- 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.
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；以官网为准).
The abstract: three moves in ≤300 words
IJOC's guidance is to cover, without notation: (1) research questions and challenges — the OR problem and why it is computationally hard; (2) methodology and results — what you designed and what it achieves; (3) importance and implications — why the computational advance matters. Lead the second move with the magnitude ("solves instances an order of magnitude larger"), not the technique name alone. Because formulas are barred, describe the method in words a non-specialist in your sub-area can follow.
The introduction: reach the contribution fast
By the end of page one the reader should know the OR problem, why existing methods fall short computationally, what you do, and by how much. Use the contribution sentence from ijoc-contribution-framing near the top, then a short bulleted list of contributions. Defer the literature deep-dive; do not open with a multi-page survey.
Method prose, equations, and pseudocode
Write algorithms as numbered pseudocode, not paragraphs; reserve prose for the idea and the invariants. Number and reference every equation you rely on. State theorem assumptions in the theorem, not three pages earlier. Define notation once, in a table if it is heavy. The reader should be able to re-implement from the paper plus the deposit — that is the IJOC standard.
Fitting the page limit
The main paper is capped at 25 pages including references, tables, and figures, with up to 10 further pages of appendices; longer appendices move to online supplements, and code/data live in the GitHub deposit (not the page count). Tighten by moving long proofs and exhaustive result tables to the supplement/deposit while keeping the main paper self-contained on its central claims — a reader must be able to follow the contribution without the supplement.
Show full SKILL.md (244 more words)Show less
Word choices that signal computational rigor
Small lexical habits mark an experienced IJOC author. Say "on standard benchmark instances" rather than "on our test problems"; "within the same time limit / at equal wall-clock" rather than "faster"; "the performance profile shows" rather than "results indicate"; "we prove" only when you do, otherwise "we observe empirically." Report numbers with their units and conditions inline (e.g., "31% root-gap reduction on the full set, single-threaded, 1-hour limit"), so a skimming reviewer absorbs the conditions with the claim. Avoid hedge-words ("somewhat," "quite") around quantitative results — give the magnitude instead. This register is what tells the Area Editor the paper was written by someone who runs experiments seriously.
Checklist
- Abstract ≤300 words, no formulas, covering questions/challenges → methodology/results → importance
- Page one delivers problem, gap, method, and magnitude
- Contribution sentence appears early and matches the abstract and conclusion
- Algorithms in numbered pseudocode; equations numbered and referenced
- Notation defined once; theorem assumptions stated locally
- Within 25 main pages (+≤10 appendix); main paper self-contained on central claims
- Voice is methods-forward — neither application essay nor formulation-free CS paper
Anti-patterns
- An abstract that summarizes the application and never states the computational advance
- A formula or heavy notation in the abstract (against IJOC guidance)
- A multi-page survey before the contribution
- Algorithms described in dense prose instead of pseudocode
- Over the page limit because raw result tables and full proofs sit in the main text
- A main paper that cannot be understood without the online supplement
Output format
【Journal】INFORMS Journal on Computing
【Skill】ijoc-writing-style
【Abstract】≤300 words, no formulas, 3 moves present? [Y/N]
【Page-one contribution】problem+gap+method+magnitude? [Y/N]
【Pseudocode/equations】algorithms numbered; equations referenced? [Y/N]
【Length】≤25pp main (+≤10 appendix); self-contained? [Y/N]
【Voice】methods-forward, not app-essay / not formulation-free CS? [Y/N]
【Next skill】ijoc-submission© 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-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ijoc Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
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…
Related
Categories
Questions about Ijoc Writing Style
What does Ijoc Writing Style do?
A skill your agent uses when the prose, abstract, or introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance or misreads the house voice. Ijoc Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when the prose, abstract, or introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance or misreads the house voice.
When should I use Ijoc Writing Style?
Ijoc Writing Style fits situations like: introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance; misreads the house voice.
How do I install Ijoc Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-writing-style -a claude-code`. Or copy the skill folder (INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ijoc-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Ijoc Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-writing-style -a codex`. Or copy the skill folder (INFORMS-Journal-on-Computing-Skills/skills/ijoc-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ijoc-writing-style in your project. Codex loads it when a task matches its description.
Can I use Ijoc Writing Style 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-writing-style -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-writing-style, .gemini/skills/ijoc-writing-style, .github/skills/ijoc-writing-style and .opencode/skills/ijoc-writing-style in your project.
What does Ijoc Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Ijoc Writing Style is instructions for the agent only.
Does Ijoc Writing Style 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 Writing Style 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 Writing Style use?
Ijoc Writing Style 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 Writing Style use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Writing Style?
Skills that share tags, products or a category with Ijoc Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ijoc Writing Style?
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.