Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/cvpr-submission
Use when auditing a CVPR submission before the OpenReview deadline, covering abstract registration and profile requirements, the 8-page limit including figures and tables, the Compute Reporting Form, anonymity and external-link bans, dual-submission attestations, reviewer-duty enrollment, and desk-reject triage.
Passed 20 of 23 test cases with the skill, and 12 of 23 without it.
and 12 more in the full report
9 fixed11 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our team wants to revise the text in the OpenReview abstract submission box to sound punchier than the abstract in our main PDF file before submitting to CVPR. Is it acceptable for the web form abstract to differ slightly from the PDF abstract?
| Checked | Without skill | With skill |
|---|---|---|
| States that the OpenReview abstract field must match the PDF abstract verbatim. | Missed | Passed |
| Explains that reviewers use the abstract field for bidding. | Passed | Passed |
The instructions your model reads when the skill loads.
Run this audit in the two weeks before the CVPR paper deadline. All specifics below are the CVPR 2026 cycle as read on 2026-07-08 (paper deadline November 13, 2025); the next Program Chairs will rewrite details, so reopen the current Author Guidelines and Dates pages at cvpr.thecvf.com before acting on any number here.
CVPR staggers three hard cut-offs a week apart, and the first one is the one teams miss:
The cap is 8 pages including figures and tables, with extra pages permitted only for
cited references. That "including figures" clause is what distinguishes CVPR budgeting
from text-limited venues: a half-page teaser figure, two qualitative grids, and three
result tables can consume four of your eight pages. Plan figures as page-budget line
items, not decorations, and treat any style-file edit, margin nudge, or font substitution
as a desk-reject trigger — over-length and mis-formatted papers are rejected without
review. Build from the official author kit (github.com/cvpr-org/author-kit), current
year's branch, unmodified.
New in the 2026 cycle: every submission carried a CRF. Only Section 1 (hardware) and Section 5 (verification) were mandatory — about five minutes of work — and a documented opt-out path existed via the comments field for proprietary or unrecorded compute. Fill the mandatory sections early; do not let a five-minute form become a deadline-night blocker, and do not fabricate GPU-hour numbers to look either frugal or mighty.
test cases passed, vs 12 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.