Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics…
Install Oopsla Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-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/OOPSLA-Skills/skills/oopsla-writing-style .claude/skills/oopsla-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 "oopsla-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-writing-style into .claude/skills/oopsla-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-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/OOPSLA-Skills/skills/oopsla-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 oopsla-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-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/OOPSLA-Skills/skills/oopsla-writing-style .agents/skills/oopsla-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 "oopsla-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-writing-style into .agents/skills/oopsla-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-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 oopsla-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-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/OOPSLA-Skills/skills/oopsla-writing-style .cursor/skills/oopsla-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 "oopsla-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-writing-style into .cursor/skills/oopsla-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-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 OOPSLA-Skills/skills/oopsla-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 oopsla-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-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/OOPSLA-Skills/skills/oopsla-writing-style .gemini/skills/oopsla-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 "oopsla-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-writing-style into .gemini/skills/oopsla-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-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 oopsla-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 oopsla-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/OOPSLA-Skills/skills/oopsla-writing-style .github/skills/oopsla-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 "oopsla-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-writing-style into .github/skills/oopsla-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-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 oopsla-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 oopsla-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/OOPSLA-Skills/skills/oopsla-writing-style .opencode/skills/oopsla-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 "oopsla-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-writing-style into .opencode/skills/oopsla-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-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
oopsla-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 438 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics…
- Revising a draft into OOPSLAs register — design insight stated before the artifact
- SKILL.md covers Voice calibration, The running example as…, Claims that survive two readings and Journal pacing inside 23 pages, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Claims written to be falsifiable
What it does
Oopsla Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics, journal-article pacing inside the 23-page cap, and honest threats-to-validity prose that preempts the revision lever rather than triggering it.
Its SKILL.md is about 1k 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
- Revising a draft into OOPSLAs register — design insight stated before the artifact
- Claims written to be falsifiable
- Motivating examples that carry semantics
- Journal-article pacing inside the 23-page cap
Example prompts
- “/oopsla-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
Oopsla Writing Style loads about 1k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 438 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). 438 words, ~1,048 tokens.
Download SKILL.mdSave it as
.claude/skills/oopsla-writing-style/SKILL.md (or your agent's skills folder).- name
- oopsla-writing-style
- description
- Use when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics, journal-article pacing inside the 23-page cap, and honest threats-to-validity prose that preempts the revision lever rather than triggering it.
OOPSLA Writing Style
An OOPSLA paper is read twice by design: once by a committee choosing among four outcomes, and again — possibly by the same people — if a revision comes back. Style at this venue therefore optimizes for checkability: a paper whose claims can be verified paragraph by paragraph collects bounded revision demands (or none), while a paper that argues by adjective collects unbounded ones. The published form is a journal article (PACMPL), and the prose should carry that register: measured, self-contained, built to be cited.
Voice calibration
| Draft habit | OOPSLA replacement |
|---|---|
| "We present NovelTool, a novel system for..." | Name the design question and your answer; the tool arrives as evidence (see resources/worked-examples/01-introduction.md) |
| "Our approach significantly outperforms..." | The number, the baseline, the workload, the dispersion — or nothing |
| "To the best of our knowledge, first..." | A positioning sentence naming the nearest prior work and the delta (oopsla-related-work) |
| "Due to space limitations, details are in the appendix" | A body-level statement of what the appendix establishes (oopsla-supplementary) |
| A wall of formalism before any example | A running example that motivates each definition as it appears |
The running example as load-bearing structure
OOPSLA's classic papers — from type-system counterexamples to
language-experience reports (resources/exemplars/library.md) — are built
around concrete programs. Choose one small example early and make it do
three jobs: expose the problem, exercise the mechanism, and mark the
boundary (show the case the mechanism does not handle). If your example
cannot demonstrate the limitation honestly, the limitation section will read
as boilerplate — reviewers notice.
Show full SKILL.md (190 more words)Show less
Claims that survive two readings
Write each contribution as a sentence with a built-in test:
Weak: "We propose an efficient analysis for X."
Strong: "The analysis decides X for programs in fragment F in O(n log n);
outside F it degrades to a sound approximation, evaluated in §6.3."
Weak: "Our semantics is more expressive."
Strong: "Every program typable under [prior] remains typable (Thm 4.1);
the converse fails on the example of §2.2."The strong forms give a Minor-Revision reviewer something bounded to check — which is exactly the outcome ladder you want to be standing on.
Journal pacing inside 23 pages
- Spend the first two pages entirely on problem, insight, and claims; a reader stopping there should be able to state your thesis.
- Sections should alternate mechanism and evidence; ten pages of design followed by two of evaluation reads as unvalidated, the inverse as unmotivated.
- Threats-to-validity and limitations get their own subsection with specific content: which claims depend on which assumptions, and what was not measured. Generic threats paragraphs are revision bait.
- Prose must not lean on the appendix for coherence; the 23 pages are the
paper (
oopsla-supplementaryfor the layering rule).
Revision-aware editing
When revising for a second round, mark the diff in prose quality too: the change log tells reviewers where you changed; the writing must make each change locally self-justifying, because continuity means your examiners remember the old text. Never quietly weaken a claim a reviewer challenged — weaken it visibly, with the reason.
Output format
[Register] design-insight-led: yes/no + first page diagnosis
[Adjective sweep] unquantified evaluatives found: <count + worst three>
[Claim audit] contributions rewritten in falsifiable form
[Example] running example present / missing / does not mark boundaries
[Pacing] mechanism-evidence alternation + limitations specificity© 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 OOPSLA-Skills/skills/oopsla-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Oopsla 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 |
|---|---|---|---|---|---|---|
| Oopsla Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | 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 Oopsla Writing Style
What does Oopsla Writing Style do?
A skill your agent uses when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics…. Oopsla Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics, journal-article pacing inside the 23-page cap, and honest threats-to-validity prose that preempts the revision lever rather than triggering it.
When should I use Oopsla Writing Style?
Oopsla Writing Style fits situations like: revising a draft into OOPSLAs register — design insight stated before the artifact; claims written to be falsifiable; motivating examples that carry semantics; journal-article pacing inside the 23-page cap.
How do I install Oopsla Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-writing-style -a claude-code`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/oopsla-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Oopsla Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-writing-style -a codex`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/oopsla-writing-style in your project. Codex loads it when a task matches its description.
Can I use Oopsla 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 oopsla-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/oopsla-writing-style, .gemini/skills/oopsla-writing-style, .github/skills/oopsla-writing-style and .opencode/skills/oopsla-writing-style in your project.
What does Oopsla Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Oopsla Writing Style is instructions for the agent only.
Does Oopsla 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 Oopsla 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 Oopsla Writing Style use?
Oopsla 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 Oopsla Writing Style use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Oopsla Writing Style?
Skills that share tags, products or a category with Oopsla 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 Oopsla 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.