wacv-submission
Use when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-submission --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 Submission Run this audit in the two weeks before a WACV **round** deadline. The specifics below are the WACV 2026/2027 cycles as read on 2026-07-09; chairs rewrite details each edition, and WACV uniquely runs **two rounds**, so reopen the current Author Guidelines, Dates page, and the correct OpenReview round group at wacv.thecvf.com before acting on any number here. ## First decision: which round, which track Two fields on the OpenReview form change everything downstream, and both are chosen before you write a word of the audit: 1. **Round 1 or Round 2.** They are *different OpenReview groups*. Round 1 (reported paper deadline June 26, 2026 for WACV 2027) gives you a rebuttal and the Revise-and-Resubmit safety net — a paper that is close but not done can be invited back rather than killed. Round 2 (reported August 28, 2026) is Accept/Reject with **no rebuttal**; it is for polished work and for revised Round 1 papers. Submitting a borderline paper straight to Round 2 throws away the mechanism WACV built to help it. 2. **Applications or Algorithms track.** The two tracks are reviewed against different criteria (systems-level innovation and comparative assessment vs algorithm
- First decision: which round, which track
- Format discipline, WACV flavor
- Anonymity and the anonymized supplement
- Desk-reject and triage table
- Final-week sequence
- Reverify each cycle
- Output format
Mechanical sweep on the final build, ten minutes before upload
pdftotext paper.pdf - | grep -nEi 'github\.com|drive\.google|project page|our (prior|previous) work' | head
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # identity in metadata
grep -rn 'vspace\|\\addtolength\|geometry' main.tex # style-tampering tells
pdftotext paper.pdf - | awk 'END{print NR" lines extracted"}' # sanity: text present, not rasterWhat does the wacv-submission skill do?
Use when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-submission --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 984 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.