iccv-writing-style

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-writing-style --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# ICCV Writing Style An ICCV submission is read by reviewers drawn from the most international pool in computer vision — in 2025, every author of 11,239 submissions was also a potential reviewer — and most of them work outside your subfield. The style target is therefore precise: a paper a *generalist vision researcher* can evaluate fairly in one sitting, in their second or third language, under deadline pressure of their own. ## Write for the generalist, cite for the specialist The three reviewers you draw will rarely all be specialists in your niche. Concretely: - Define subfield jargon at first use, in one clause, even terms your lab considers standard ("the chamfer-L1 metric, i.e. average nearest-neighbor distance in both directions"). - Make the method's *mechanism* explainable to an adjacent-area reviewer: what information flows where, and what would break without it. Specialists verify details; generalists score the story — you need both. - Prefer short declarative sentences. Non-native readers (and tired native ones) lose subordinate-clause chains; ICCV's reviewer pool is global by construction, and prose that filters readers filters scores. ## The inclusive-8-pages economy

Skim-pass simulator: what a reviewer sees in the first five minutes
pdftotext -layout paper.pdf - | grep -A2 -E '^(Figure|Table) [0-9]+[.:]' > skim.txt
head -60 skim.txt   # does this sequence state problem → idea → evidence?