wacv-writing-style
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 sy
- Write for your track
- The first-page arc
- Figures are page budget
- Scope every claim
- Compress for eight pages
- Reverify each cycle
- Output format
What does the wacv-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.