cvpr-camera-ready
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-camera-ready --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 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 witho
- Where the paper actually ends up
- De-anonymization without breakage
- The dataset clause has a deadline
- Oral, highlight, or poster: what changes
- Final-PDF quality assurance
- Synchronizing the public record
- Reverify each cycle (all 待核实 for the current year)
- Output format
Release-readiness probe, run from a machine outside your institution curl -sIL https://<dataset-host>/<archive> | grep -Ei 'HTTP|content-length' sha256sum downloaded_archive.tar.gz # matches the checksum printed in the repo? python3 - <<'EOF'
What does the cvpr-camera-ready skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-camera-ready --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.