wacv-reproducibility
Use when strengthening the reproducibility of a WACV paper, covering the recipe ledger for constraint-aware systems, benchmark and split hygiene, seed and session honesty, device and power reporting for applications claims, and keeping the reproduction package in sync with the paper across the two-round Revise-and-Resubmit lap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-reproducibility --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 Reproducibility Use this to make a WACV result checkable — by a reviewer now and by you at the Round 2 resubmission. WACV's applications framing raises the bar in one direction (a systems claim must be reproducible *as deployed*), and the two-round model adds a second (paper and artifact must not drift between rounds). Facts are the WACV 2026/2027 cycles as read on 2026-07-09. ## The recipe ledger Keep one ledger that regenerates every reported number, so the body, the supplement, and the artifact cannot diverge: | Ledger entry | Why WACV cares | |---|---| | Exact data splits and preprocessing | Applications datasets are often custom; a hidden split invalidates a comparison | | Seeds (and sessions/devices for field work) | Reviewers distrust single hero runs | | Hyperparameters per reported row | Lets a reviewer see the comparison was matched | | **Device, power meter, and measurement method** | An applications latency/wattage claim is only reproducible if the rig is named | | Baseline re-tuning under your constraint | Proves the comparison was fair, not defaults-vs-yours | | Script → figure/table mapping | So a Round 2 reviewer confirms nothing changed silently | ## Constra
- The recipe ledger
- Constraint-aware reproducibility
- Seed and session honesty
- Sync across the two rounds
- Reverify each cycle
- Output format
What does the wacv-reproducibility skill do?
Use when strengthening the reproducibility of a WACV paper, covering the recipe ledger for constraint-aware systems, benchmark and split hygiene, seed and session honesty, device and power reporting for applications claims, and keeping the reproduction package in sync with the paper across the two-round Revise-and-Resubmit lap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-reproducibility --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.