iccv-related-work
Use when positioning an ICCV paper against the literature, covering the intervening-cycle problem of citing a CVPR and an ECCV that happened since the last ICCV, concurrent-preprint etiquette around the March deadline, double-blind self-reference and the do-not-cite-your-repo rule, and venue-attribution hygiene across the vision big three.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work --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 Related Work Positioning at ICCV has a built-in time-lapse problem: between one ICCV and the next, a full CVPR cycle and a full ECCV cycle (and usually a second CVPR) have deposited their papers. Your related-work section is judged on whether it metabolized *those*, not on whether it knows the classics. This skill organizes the section around that clock. ## The intervening-cycle sweep Before writing a word, sweep the venues that published since the last ICCV in your area, newest first: ```text sweep order for an ICCV 2027 submission (deadline 待核实, ~early 2027) 1. CVPR 2026 proceedings + late-2026 arXiv ← your reviewers' own papers 2. ECCV 2026 proceedings 3. ICCV 2025 proceedings ← the venue's own last word 4. CVPR 2025 5. journals/others (TPAMI, IJCV, NeurIPS) same window 6. classics that define the problem (pre-window) ``` The most common positioning failure at biennial venues is a related-work section written when the project started — 18 months stale by the deadline. Diff your .bib's newest entry date against the deadline; a gap over ~4 months means the sweep never re-ran. ## Nearest neighbors get the words Reviewers do not need coverage; they need to see that you know w
- The intervening-cycle sweep
- Nearest neighbors get the words
- Concurrency at a March deadline
- Double-blind reference mechanics
- Venue attribution: the big-three trap
- Organize by question, close with the gap
- Positioning against the two-year echo
- Reverify each cycle
- Output format
grep -c '@' main.bib grep -B1 -iE 'journal.*arxiv|eprint' main.bib | grep -iE 'year.*20(1[0-9]|2[0-3])' | head grep -iE 'booktitle.*(ICCV|CVPR|ECCV)' main.bib | sort | uniq -c
What does the iccv-related-work skill do?
Use when positioning an ICCV paper against the literature, covering the intervening-cycle problem of citing a CVPR and an ECCV that happened since the last ICCV, concurrent-preprint etiquette around the March deadline, double-blind self-reference and the do-not-cite-your-repo rule, and venue-attribution hygiene across the vision big three.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work --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.