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 WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the…
Install Wacv Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-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/WACV-Skills/skills/wacv-writing-style .claude/skills/wacv-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 "wacv-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-writing-style into .claude/skills/wacv-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-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/WACV-Skills/skills/wacv-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 wacv-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-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/WACV-Skills/skills/wacv-writing-style .agents/skills/wacv-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 "wacv-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-writing-style into .agents/skills/wacv-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-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 wacv-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-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/WACV-Skills/skills/wacv-writing-style .cursor/skills/wacv-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 "wacv-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-writing-style into .cursor/skills/wacv-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-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 WACV-Skills/skills/wacv-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 wacv-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-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/WACV-Skills/skills/wacv-writing-style .gemini/skills/wacv-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 "wacv-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-writing-style into .gemini/skills/wacv-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-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 wacv-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 wacv-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/WACV-Skills/skills/wacv-writing-style .github/skills/wacv-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 "wacv-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-writing-style into .github/skills/wacv-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-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 wacv-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 wacv-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/WACV-Skills/skills/wacv-writing-style .opencode/skills/wacv-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 "wacv-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-writing-style into .opencode/skills/wacv-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-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
wacv-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 477 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 WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the…
- Revising a WACV papers prose and first page
- SKILL.md covers Write for your track, The first-page arc, Figures are page budget and Scope every claim, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering how to write for the chosen Applications
What it does
Wacv Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the method, self-contained figure captions inside the 8-page-including-figures budget, scoped claims, and a first page that pre-empts the Revise-and-Resubmit question.
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 WACV papers prose and first page
- Covering how to write for the chosen Applications
- Algorithms track
- Leading with the real-world constraint
Example prompts
- “/wacv-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
Wacv Writing Style loads about 1k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 477 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). 477 words, ~1,032 tokens.
Download SKILL.mdSave it as
.claude/skills/wacv-writing-style/SKILL.md (or your agent's skills folder).- name
- wacv-writing-style
- description
- Use when revising a WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the method, self-contained figure captions inside the 8-page-including-figures budget, scoped claims, and a first page that pre-empts the Revise-and-Resubmit question.
WACV Writing Style
Use this to make a WACV paper read the way its reviewers judge it. The governing fact is the two-round model: a first page that answers the reviewer's obvious question earns Accept; one that leaves it open earns Revise and Resubmit. Facts are the WACV 2026/2027 cycles as read on 2026-07-09.
Write for your track
The two tracks reward different first pages, and writing to the wrong one draws the wrong review:
| If your track is… | Lead the first page with… | The reviewer is asking… |
|---|---|---|
| Applications | The real-world constraint and why existing methods break under it | Does this system actually work under the deployment constraint you name? |
| Algorithms | The method/mechanism and the matched-baseline comparison | Is the algorithmic idea new, and does the gain survive fair comparison? |
An Applications paper that opens with "a novel attention module" and an Algorithms paper that opens with "an important real-world problem" have each buried their contribution under the other track's framing.
The first-page arc
Put the contribution in the first page: problem/constraint → why prior methods are insufficient (each named) → method or system → evidence → why it fits the track. Every major claim on that page should point to a figure, a table, or a section — not to a promise. Because WACV reviewers see three reviews reconciled by an AC, a page that a busy reader can summarize in two sentences travels further than a dense one.
Figures are page budget
The cap is 8 pages including figures and tables. A teaser, two qualitative grids, and three result tables can eat half the paper, so design figures as line items:
- One teaser that states the contribution visually, with a self-contained caption a reviewer can read without the body.
- Qualitative results that a reviewer will judge by eye — check they render at print zoom.
- Tables that report the comparison under the stated condition, with uncertainty.
Caption test (apply to every figure):
Can a reviewer who reads ONLY this caption state (a) what is shown and
(b) what it demonstrates about the claim? If not, rewrite the caption, not the body.Show full SKILL.md (166 more words)Show less
Scope every claim
WACV's applications framing punishes overclaiming quickly, because a reviewer can often name the deployment case you did not test. Scope claims to the domain, constraint, and hardware you actually demonstrated ("row-crop segmentation at 2 W in sub-10-lux light"), and disclaim what you did not show. A scoped claim that holds beats a broad claim a reviewer can break in one sentence — and broken claims are what turn into revision requests.
Compress for eight pages
- Move protocol detail, extra qualitative results, and derivations to the anonymized
supplement (see
wacv-supplementary), keeping the body's argument intact. - Cut roadmap sentences that restate the table of contents; spend the space on the gap paragraph, where reviewers form their opinion.
- Keep notation and baselines consistent between body and supplement so a Round 2 reviewer re-reading a revised paper is never confused by a moved number.
Reverify each cycle
- The 8-page-including-figures rule and the references-only overflow.
- The two-track review criteria and any track-specific formatting.
- The author-kit style version.
Output format
[Track fit] first page leads with the right thing for <Applications|Algorithms>: yes/no
[First-page arc] constraint/method → gap → evidence present: yes/no
[Figure budget] pages spent on figures/tables: <n of 8> · captions self-contained: yes/no
[Overclaim risk] <claim a reviewer could break> → scoped: yes/no
[Compression] what moves to supplement: <list>© 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 WACV-Skills/skills/wacv-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wacv 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 |
|---|---|---|---|---|---|---|
| Wacv 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 Wacv Writing Style
What does Wacv Writing Style do?
A skill your agent uses when revising a WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the…. Wacv Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when revising a WACV paper's prose and first page, covering how to write for the chosen Applications or Algorithms track, leading with the real-world constraint or the method, self-contained figure captions inside the 8-page-including-figures budget, scoped claims, and a first page that pre-empts the Revise-and-Resubmit question.
When should I use Wacv Writing Style?
Wacv Writing Style fits situations like: revising a WACV papers prose and first page; covering how to write for the chosen Applications; algorithms track; leading with the real-world constraint.
How do I install Wacv Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-writing-style -a claude-code`. Or copy the skill folder (WACV-Skills/skills/wacv-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wacv-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Wacv Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-writing-style -a codex`. Or copy the skill folder (WACV-Skills/skills/wacv-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wacv-writing-style in your project. Codex loads it when a task matches its description.
Can I use Wacv 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 wacv-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/wacv-writing-style, .gemini/skills/wacv-writing-style, .github/skills/wacv-writing-style and .opencode/skills/wacv-writing-style in your project.
What does Wacv Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Wacv Writing Style is instructions for the agent only.
Does Wacv 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 Wacv 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 Wacv Writing Style use?
Wacv 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 Wacv Writing Style use?
About 1k tokens (SKILL.md is roughly 4.1k 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 Wacv Writing Style?
Skills that share tags, products or a category with Wacv 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 Wacv 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.