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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-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.
# CVPR Submission 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. ## The three deadlines that catch people CVPR staggers three hard cut-offs a week apart, and the first one is the one teams miss: 1. **Abstract registration + OpenReview profiles** (Nov 6, 2025 in the 2026 cycle). Every listed author — including the advisor added "later" and the intern who wrote one module — needed a complete, valid OpenReview profile by this date. An incomplete profile on any coauthor is desk-reject exposure for the paper. 2. **Full paper** (Nov 13, 2025, 11:59pm AoE, announced as unmovable). The PDF, the author list, subject areas, conflicts, and the **Compute Reporting Form** all land here. 3. **Supplementary material** (Nov 20, 2025, AoE). One extra week — but only for the supplement; nothing in the main PDF can change after the paper deadline. ## Page discipline, CVPR flavor The cap is **8 pages including figures and tables**,
- The three deadlines that catch people
- Page discipline, CVPR flavor
- The Compute Reporting Form
- Anonymity and the external-link ban
- Dual submission and the media embargo
- Reviewer duty is part of submitting
- Desk-reject triage
- OpenReview form fields worth drafting early
- Final 72 hours, in order
- 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 cvpr-submission skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-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 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.