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 UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and…
Install Uai Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-writing-style .claude/skills/uai-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 "uai-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-writing-style into .claude/skills/uai-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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/UAI-Skills/skills/uai-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 uai-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-writing-style .agents/skills/uai-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 "uai-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-writing-style into .agents/skills/uai-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 uai-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-writing-style .cursor/skills/uai-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 "uai-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-writing-style into .cursor/skills/uai-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 UAI-Skills/skills/uai-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 uai-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-writing-style .gemini/skills/uai-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 "uai-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-writing-style into .gemini/skills/uai-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 uai-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 uai-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/UAI-Skills/skills/uai-writing-style .github/skills/uai-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 "uai-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-writing-style into .github/skills/uai-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 uai-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 uai-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/UAI-Skills/skills/uai-writing-style .opencode/skills/uai-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 "uai-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-writing-style into .opencode/skills/uai-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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
uai-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 780 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 UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and…
- Revising a UAI manuscript for probabilistic-inference readers
- SKILL.md covers Notation is the first review, Assumptions carry the argument, The 8-page main part as an… and Calibrated prose, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Enforcing precise notation for distributions
What it does
Uai Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and identifiability statements, an 8-page main part that carries the whole argument while proofs sit in the appendix, and claims calibrated to what the theory and experiments show.
Its SKILL.md is about 1.6k 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 UAI manuscript for probabilistic-inference readers
- Enforcing precise notation for distributions
- Explicit assumption and identifiability statements
- An 8-page main part that carries the whole argument while proofs sit in the appendix
Example prompts
- “/uai-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 (its code samples are latex).
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
Uai Writing Style loads about 1.6k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 780 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). 780 words, ~1,650 tokens.
Download SKILL.mdSave it as
.claude/skills/uai-writing-style/SKILL.md (or your agent's skills folder).- name
- uai-writing-style
- description
- Use when revising a UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and identifiability statements, an 8-page main part that carries the whole argument while proofs sit in the appendix, and claims calibrated to what the theory and experiments show.
UAI Writing Style
Use this during revision. The UAI readership lives on probabilistic reasoning, graphical models, causality, and Bayesian methods, and the posted review criteria end with "clarity of writing" as a first-class axis. At this venue clarity is mostly a formal property: whether every symbol, assumption, and probability statement means exactly one thing.
Notation is the first review
Probabilistic papers die by notation drift more than by grammar. Enforce a single notational regime before polishing sentences:
- One symbol per object: if
pis a density, do not let it moonlight as a probability mass function and a marginal without saying so. - Distinguish conditioning from intervention typographically everywhere:
p(y | x)versusp(y | do(x)); a causality paper that blurs this once loses its causal readers. - Declare graph notation on first use — nodes, parents
pa(V), whether graphs are DAGs, MAGs, or CPDAGs — and never switch mid-paper. - Fix measure-theoretic hygiene where it matters (densities exist with respect to what?), and say nothing about it where it does not; ostentatious rigor on trivialities reads as inexperience.
% Preamble discipline: define once, use everywhere
\newcommand{\E}{\mathbb{E}}
\newcommand{\indep}{\perp\!\!\!\perp} % conditional independence
\newcommand{\do}[1]{\mathrm{do}(#1)} % interventions, always \do{x}
\newtheorem{assumption}{Assumption} % A1, A2... citable by label
% Every theorem names its assumptions explicitly:
% \begin{theorem}[Identifiability]\label{thm:id}
% Under Assumptions~\ref{a:faithful} and \ref{a:positivity}, ...Assumptions carry the argument
- Give each assumption a number and a name, state it once, and cite it by label inside every result that uses it. UAI reviewers audit which assumption powers which theorem; make that audit trivially easy.
- Say early which assumptions are standard, which are novel, and which are restrictive — and for the restrictive ones, what breaks without them. Preempting "A3 is strong" in the text is worth a rebuttal round.
- Identifiability claims deserve their own sentence structure: what is identified, from what observational or interventional regime, under which assumptions. Compressed versions of that sentence become wrong versions.
The 8-page main part as an argument spine
With unlimited appendices in the same PDF, the 8 pages are pure argument budget. Spend them so a reviewer can reach a verdict on correctness, novelty, and backing without opening the appendix — and needs the appendix only to verify:
- Page 1 states the inference problem, why existing treatment of uncertainty fails, the contribution, and the strongest guarantee or empirical finding.
- Every theorem in the body gets a proof sketch conveying the mechanism; the appendix holds the full argument.
- Every experimental claim in the body gets its central table or figure; per-dataset breakdowns move back.
- Related work earns its space by sharpening the delta, not by demonstrating erudition.
Calibrated prose
A venue about uncertainty notices overconfident language immediately.
| Overclaimed | Calibrated for UAI |
|---|---|
| "Our method outperforms all baselines" | "Improves over X and Y on 5 of 6 datasets (mean ± sd over 10 seeds); ties on Z" |
| "The posterior is accurate" | "R-hat ≤ 1.01 on all parameters; ESS > 400 per chain" |
| "Our intervals are well calibrated" | "Empirical coverage 89.3% ± 0.8 at nominal 90%" |
| "Works for any graphical model" | "Applies to discrete pairwise MRFs; extensions in App. E" |
| "First to study X" | "To our knowledge, the first identifiability result for X under A1–A2" |
Symmetrically, do not under-claim guarantees you actually prove — "may help in some settings" wastes a theorem.
Show full SKILL.md (286 more words)Show less
First-page arc, checkable
The opening page should let a bidding reviewer and a skimming AC reconstruct the paper. Verify each element exists and appears in roughly this order:
- The inference problem, stated as a probabilistic question (what is unknown, what is observed, what regime).
- Why current uncertainty handling fails — named per method family, not "prior work has limitations".
- The contribution as an object: estimator, bound, graph class, algorithm, identification condition.
- The attached guarantee or diagnostic, with its key assumption named inline.
- One headline number or theorem pointer a reader could verify later.
- Vocabulary matching the CFP's topic list, so bidding routes correctly.
- Nothing on page 1 that the appendix cannot back.
Sentence-level habits for this audience
- Lead paragraphs with the probabilistic object ("The posterior over structures...", not "It can be seen that...").
- Keep inline math out of load-bearing sentences where a display would let the reader check indices.
- Write the abstract as: problem, gap in uncertainty handling, method or result, guarantee or diagnostic, headline evidence. UAI abstracts also drive reviewer bidding, so name the model class and the contribution type explicitly.
- Anonymize style too: distinctive lab phrasing plus first-person history ("in previous work we showed") undermines double-blind review.
Titles that route correctly
UAI titles are unusually literal, and bidding rewards that: name the object and the regime ("Identifiability of X under Y", "Unbiased Z estimation via W") rather than branding a system name. A memorable acronym can ride along after a colon, but the pre-colon half should let a reviewer decide "mine" or "not mine" in one read. Avoid question titles and avoid claiming words ("optimal", "exact") the paper then qualifies — at this venue the title is the first claim checked against the evidence.
Output format
[Notation audit] consistent / drift found at: <symbols, sections>
[Assumption ledger] labeled? cited-by-label in each theorem? novel ones flagged?
[Spine check] verdict reachable from 8 pages alone? weakest section: <n>
[Claim calibration] <overclaims and underclaims with suggested rewording>
[Bid signal] abstract names model class + contribution type? © 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 UAI-Skills/skills/uai-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uai 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 |
|---|---|---|---|---|---|---|
| Uai Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 Uai Writing Style
What does Uai Writing Style do?
A skill your agent uses when revising a UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and…. Uai Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a UAI manuscript for probabilistic-inference readers, enforcing precise notation for distributions, graphs, and interventions, explicit assumption and identifiability statements, an 8-page main part that carries the whole argument while proofs sit in the appendix, and claims calibrated to what the theory and experiments show.
When should I use Uai Writing Style?
Uai Writing Style fits situations like: revising a UAI manuscript for probabilistic-inference readers; enforcing precise notation for distributions; explicit assumption and identifiability statements; an 8-page main part that carries the whole argument while proofs sit in the appendix.
How do I install Uai Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-writing-style -a claude-code`. Or copy the skill folder (UAI-Skills/skills/uai-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uai-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Uai Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-writing-style -a codex`. Or copy the skill folder (UAI-Skills/skills/uai-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uai-writing-style in your project. Codex loads it when a task matches its description.
Can I use Uai 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 uai-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/uai-writing-style, .gemini/skills/uai-writing-style, .github/skills/uai-writing-style and .opencode/skills/uai-writing-style in your project.
What does Uai Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Uai Writing Style is instructions for the agent only.
Does Uai 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 Uai 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 Uai Writing Style use?
Uai 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 Uai Writing Style use?
About 1.6k tokens (SKILL.md is roughly 6.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 Uai Writing Style?
Skills that share tags, products or a category with Uai 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 Uai 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.