iccv-submission
Use when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day paper-plus-supplement upload, the 8-page inclusive format, the 25-submissions-per-author cap, every-author reviewer enrollment, anonymity and media-embargo rules, and desk-reject triage.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-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.
# ICCV Submission This is the pre-flight audit for an ICCV upload. Anchors are the ICCV 2025 cycle (registration March 3; paper **and** supplementary material March 7, 2025, 11:59pm HST; verified via official-page renderings on 2026-07-08). The 2027 cycle had published no instructions at check time — re-read the live Author Guidelines, Dates, and Submission Checklist pages before acting on any number below. ## One upload event, not two ICCV 2025 deliberately merged what its CVF siblings stagger: the main paper and the supplementary archive were due together. The consequences for your audit: - The supplement must pass the same review-readiness bar as the paper *on the same night* — schedule its freeze for the same internal deadline. - There is no post-deadline week to render videos, scrub code, or fix a corrupt zip. A supplement that fails to upload is simply absent from review. - Registration (title, abstract, author list, complete OpenReview profiles for everyone) closes days earlier. After it, you cannot add authors casually — the list you register is the list you defend. ## The three caps to check mechanically | Cap | 2025 value | Consequence of violation | |---|---|---| | Page
- One upload event, not two
- The three caps to check mechanically
- Reviewer enrollment is part of this form
- Anonymity, ICCV wording
- Mechanical sweep, deadline week
- Form fields that bite at midnight
- Triage table for the final 48 hours
- Withdrawal is also a form action
- Cycle-volatility ledger
- Output format
Run against the final PDF and the supplement archive together pdftotext iccv_final.pdf - | grep -niE 'acknowledg|grant no|our (code|repo) at|github\.com/[a-z]' | head pdfinfo iccv_final.pdf | grep -iE 'author|creator|title' # metadata identity unzip -l supplement.zip | grep -iE '\.git|DS_Store|home/|users/' # path leaks in the archive grep -rn 'setlength\|newgeometry\|baselinestretch' *.tex # style tampering tells pdftotext iccv_final.pdf - | grep -c '' # >0 lines: text layer intact
What does the iccv-submission skill do?
Use when auditing an ICCV submission in the weeks before the early-March deadline, covering OpenReview registration and profile completeness, the single same-day paper-plus-supplement upload, the 8-page inclusive format, the 25-submissions-per-author cap, every-author reviewer enrollment, anonymity and media-embargo rules, and desk-reject triage.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-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.