cvpr-reproducibility
Use when hardening a CVPR paper's reproducibility story, covering the Compute Reporting Form's hardware and compute sections, training-recipe disclosure, benchmark protocol and split hygiene, seed and variance reporting for vision experiments, and closing the gaps reviewers probe at a benchmark-driven venue.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-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.
# CVPR Reproducibility At CVPR, reproducibility failures rarely look like fraud; they look like a table nobody can match because one augmentation flag, one crop size, or one pretraining corpus went unstated. This skill hardens the paper against that fate, anchored in the 2026-cycle machinery (checked 2026-07-08): the Compute Reporting Form, the anonymous supplement, and reviewers trained on a decade of un-reproducible state-of-the-art claims. ## The CRF as a reproducibility floor The 2026 cycle attached a Compute Reporting Form to every submission — Section 1 (hardware specification) and Section 5 (verification) mandatory, deeper sections optional, with an explicit opt-out route for proprietary constraints. Treat the mandatory floor as the start, not the ceiling: | CRF layer | What it pins down | Why reviewers care | |---|---|---| | Hardware (mandatory) | GPU model, count, primary configuration | Grounds every "real-time" and "efficient" claim | | Verification (mandatory) | Author attestation | Somebody owns the numbers | | Task/compute (optional) | GPU-hours or FLOPs per result | Separates a 4-GPU method from a 512-GPU method | | Full logs (optional) | Run-level records | The stro
- The CRF as a reproducibility floor
- The recipe ledger
- Benchmark hygiene that survives scrutiny
- Variance at vision scale
- Determinism knobs, documented once
- Statement-level honesty
- Held-out evaluation servers
- Reverify each cycle
- Output format
What does the cvpr-reproducibility skill do?
Use when hardening a CVPR paper's reproducibility story, covering the Compute Reporting Form's hardware and compute sections, training-recipe disclosure, benchmark protocol and split hygiene, seed and variance reporting for vision experiments, and closing the gaps reviewers probe at a benchmark-driven venue.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-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 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.