Use when preparing the final version of an accepted CVPR paper, covering de-anonymization, the dataset-release-by-camera-ready obligation, CVF open access versus the IEEE Xplore version of record, oral/highlight/poster preparation at conference scale, and arXiv/preprint synchronization after acceptance.
SkillScore82Maintained
Automatic
◆Research pack
Last verified 9/1/2026
What it changes
Passed 18 of 22 test cases with the skill, and 13 of 22 without it.
Without skill59%
With skill82%
Checks it passed that the model alone missed
Validates license and contact fields inside the metadata JSON file
Includes a curl command probing HTTP status and Content-Length headers
States that public dataset availability must be active by the camera-ready deadline
and 5 more in the full report
5 fixed13 passed either way4 still failing0 broke
Pass-rate lift
+23 pp
Tokens
+29%
Agent turns
0%
Response time
-19%
Model gemini-3.6-flashMeasured 9/1/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Our CVPR 2026 paper claiming a new fine-grained video dataset was accepted for an oral presentation. We've unblinded the author list, added our grant numbers to the acknowledgements section, replaced anonymous links with our GitHub repo URL, and updated tables based on rebuttal promises. Please run a camera-ready audit on our submission package and format the report with these exact fields:
[Camera-ready status]
[Version-of-record checks]
[Dataset clause]
[Tier prep]
[Public sync]
[待核实 items]
What was checked, without and with the skill
Checked
Without skill
With skill
Uses the exact inline bracketed status fields format for reporting camera-ready status
Missed
Passed
Includes the dataset deadline requirement that public release must occur no later than the camera-ready deadline
Missed
Passed
Lists year-specific mechanical items such as exact page allowance and IEEE e-forms under unverified items
Missed
Passed
case-01 · gemini-3.6-flash · 9/1/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md120 linessingle file
CVPR Camera-Ready
Use this after a CVPR acceptance (decisions landed February 20 in the 2026 cycle,
conference in early June). The verified 2026 publication pipeline is described below;
the mechanical camera-ready details for any given year — exact deadline, page
allowance, IEEE forms — were not fetchable at check time and are 待核实: read the
instructions email and the current Author Guidelines before building the final PDF.
Where the paper actually ends up
Accepted CVPR papers are published twice, and the two copies serve different audiences:
CVF open access (openaccess.thecvf.com): free to everyone, posted around the
conference; the file is the accepted version apart from a watermark. This is the copy
the field reads and the one bibliography tools usually find first.
IEEE Xplore: the version of record, under IEEE Computer Society co-sponsorship.
Institutional reporting and some citation databases key off this one.
There is no author-side publication fee; costs ride on registration. Consequence for
you: the PDF you upload at camera-ready is the artifact of record in both channels —
there is no copy-editing pass to catch your mistakes.
De-anonymization without breakage
Reversing double-blind is edit work, not a switch:
Restore authors, affiliations, and emails in the final class-file mode.
Write real acknowledgements (grants, compute donors) — banned during review, expected
now.
Convert third-person self-citations back where the prose became misleading ("[12]
showed" → "we showed in [12]" only where it clarifies lineage).
Replace every "anonymous supplementary" pointer with live URLs: code repo, project
page, dataset host. Links were banned at submission; the camera-ready is where they
belong.
Rebuild and re-read — de-anonymization routinely reflows line breaks and can push a
tight page over whatever the final-version limit is that year.
The dataset clause has a deadline
Verified 2026 policy: if the paper claims a **dataset release as a scientific