cvpr-workflow
Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-workflow --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 Workflow CVPR is an annual machine with one intake: in the 2026 cycle, abstracts November 6, papers November 13, supplements November 20, rebuttal late January, decisions February 20, conference June 3–7 in Denver. This skill turns that spine into a project plan with owners, because CVPR deadline weeks are lost to coordination failures more often than to science failures. ## Campaign calendar (2026-cycle anchors) | When | Milestone | Owner discipline | |---|---|---| | T–10 weeks (early Sep) | Freeze scope: claims, benchmarks, baselines | PI + first author sign one paragraph | | T–8 weeks | Experiment matrix running; recipe ledger live | Every table row has a config | | T–6 weeks | First full draft; flip-test the figures | Co-authors annotate, don't rewrite | | T–4 weeks (early Oct) | OpenReview profiles audited for every author | One named owner; new coauthors close the list | | T–1 week (Nov 6) | **Abstract registered; profiles valid** | Desk-reject exposure if missed | | Nov 13 | **Paper + CRF submitted** | Freeze 24h early; upload before the panic hour | | Nov 20 | **Supplement uploaded** | Videos/code packaged per `cvpr-supplementary` | | Dec – Jan 12 | Coauthors deliver
- Campaign calendar (2026-cycle anchors)
- The two windows people fail to defend
- Reviewer duty as a planned workload
- Multi-paper coordination
- The resubmission ladder
- Deadline fortnight, day by day
- Cycle-status note
- Output format
What does the cvpr-workflow skill do?
Use when planning a CVPR submission campaign end to end, covering the November abstract/paper/supplement deadline chain, coauthor reviewer-duty scheduling, the January rebuttal sprint, February decisions, camera-ready and June conference logistics, and the resubmission ladder across ICCV, ECCV, and the next CVPR.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-workflow --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.