eccv-related-work
Use when positioning an ECCV submission in the literature — covering the two intervening CVPR/ICCV cycles since the last ECCV, March-deadline concurrent-work conventions, the no-self-repo citation rule, Springer-vs-CVF venue attribution hygiene, and turning a numbered LNCS bibliography into an argument.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eccv-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.
# ECCV Related Work Use this when auditing novelty positioning for ECCV. The venue's cadence sets the task: since the previous ECCV, **two CVPRs and one ICCV** have published — for a 2026 submission, that means CVPR 2024, ICCV 2025, and CVPR 2025 (plus early-2026 arXiv) all landed after ECCV 2024. A related-work section that stops at the last even year reads as two years stale. ## Coverage sweep, ordered by reviewer expectation 1. **The direct lineage**: the three to five papers your method visibly descends from, with the mechanism-level difference stated per paper. 2. **The intervening cycles**: CVPR/ICCV work from the odd-year gap that attacks the same task — the in-niche reviewer's first check. 3. **The concurrent band**: arXiv papers within a few months of the March deadline; conventions below. 4. **The classical root**: pre-deep or early-deep work the task descends from — European panels notice (and reward) correct genealogy more than most venues. ## Concurrent-work conventions around a March deadline - Treat unpublished arXiv work from the months near the deadline as concurrent: cite it, mark it "(concurrent)", compare qualitatively if feasible, but reviewers cannot require y
- Coverage sweep, ordered by reviewer expectation
- Concurrent-work conventions around a March deadline
- Venue attribution hygiene
- Making numbered citations argue
- Differentiation stress test
- Output format
What does the eccv-related-work skill do?
Use when positioning an ECCV submission in the literature — covering the two intervening CVPR/ICCV cycles since the last ECCV, March-deadline concurrent-work conventions, the no-self-repo citation rule, Springer-vs-CVF venue attribution hygiene, and turning a numbered LNCS bibliography into an argument.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill eccv-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.