A skill your agent uses 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…
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-related-work --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ICCV-Skills/skills/iccv-related-work .claude/skills/iccv-related-work && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "iccv-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-work into .claude/skills/iccv-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-related-work", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-workType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-related-work --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ICCV-Skills/skills/iccv-related-work .agents/skills/iccv-related-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iccv-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-work into .agents/skills/iccv-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-related-work", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-related-work --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ICCV-Skills/skills/iccv-related-work .cursor/skills/iccv-related-work && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iccv-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-work into .cursor/skills/iccv-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-related-work", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ICCV-Skills/skills/iccv-related-work--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-related-work --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ICCV-Skills/skills/iccv-related-work .gemini/skills/iccv-related-work && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "iccv-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-work into .gemini/skills/iccv-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-related-work", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-related-workInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ICCV-Skills/skills/iccv-related-work .github/skills/iccv-related-work && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "iccv-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-work into .github/skills/iccv-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-related-work", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iccv-related-work --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ICCV-Skills/skills/iccv-related-work .opencode/skills/iccv-related-work && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iccv-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICCV-Skills/skills/iccv-related-work into .opencode/skills/iccv-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iccv-related-work", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
iccv-related-workA skill your agent uses 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…
Iccv Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review, Academic paper search and Positioning and messaging. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Iccv Related Work loads about 1.7k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 782 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 782 words, ~1,678 tokens.
.claude/skills/iccv-related-work/SKILL.md (or your agent's skills folder).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.
Before writing a word, sweep the venues that published since the last ICCV in your area, newest first:
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.
Reviewers do not need coverage; they need to see that you know which two or three papers a skeptic would call equivalent, and why they are not. For each nearest neighbor spend three sentences: what it does (credit, accurately), where the mechanisms diverge (the actual delta), and what the divergence costs or buys (the consequence). Divergence stated as adjectives ("more efficient and more general") is what draws the "limited novelty" review; divergence stated as mechanism ("[31] fuses at the feature level and therefore needs paired data; we fuse at the loss level and train unpaired") is what preempts it.
The weeks before an ICCV deadline coincide with the post-CVPR-decision preprint wave (CVPR decisions land in February), so collisions are structural, not bad luck. Working norms:
| Situation | Handling |
|---|---|
| Preprint appeared within ~2 months of the deadline | Cite as concurrent in a short note; no obligation to outperform |
| Preprint predates your submission by a season | It is prior work; compare properly or scope your claim |
| Reviewer cites a "missing baseline" that is concurrent | Rebuttal answers with dates, one calm sentence |
| Your own preprint is on arXiv | Legal at ICCV (2025 policy: arXiv posting is not an anonymity violation); do not cite it as yours |
| A concurrent paper supersedes yours before the deadline | The honest move is repositioning before submission, not hoping reviewers missed it — they wrote it |
ICCV's 2025 anonymity guidance has one wrinkle beyond standard third-person self-citation: do not cite your public codebase — say code "will be made publicly available" instead of linking a repo that names your lab. The standard rules still apply on top: prior work of yours is "[17] showed", never "our earlier work"; no acknowledgements; no grant IDs; and no citation hole where your obvious prior paper should be, because an expert reviewer reads the gap as a signature.
Vision citations rot toward the wrong sibling, and ICCV papers misattributed to CVPR (or vice versa) appear in published bibliographies every cycle. Ground truth for the confusable landmarks:
Mechanical hygiene before the deadline:
# .bib venue hygiene, ten minutes
grep -c '@' main.bib
grep -B1 -iE 'journal.*arxiv|eprint' main.bib | grep -iE 'year.*20(1[0-9]|2[0-3])' | head
# → old arXiv-only entries: check dblp for the published venue and upgrade
grep -iE 'booktitle.*(ICCV|CVPR|ECCV)' main.bib | sort | uniq -c
# → spot-check 5 entries per venue against dblp / CVF open accessWrong venues signal carelessness; citations to papers that do not exist are far worse — under CVF-family policy, fabricated references (a known failure of machine-drafted bibliographies) can sink the paper regardless of who typed them.
Structure the section as the two or three questions the field has been asking, not as a tour of research groups. Each paragraph: the question, the families of answers with their mechanisms and limits, and a closing sentence that names what remains unsolved — which must be exactly what your paper solves. A reviewer should be able to read only the final sentence of each paragraph and reconstruct your claim's coordinates. If the last ICCV's own papers appear nowhere in this story, either the sweep failed or the venue is wrong — reviewers notice when a submission ignores the conference's own lineage.
A subtlety unique to the cadence: work you compare against from ICCV 2025 has had two years of follow-ups by the 2027 deadline. Compare against the current best version of an idea (often a CVPR/ECCV successor), while citing the ICCV original for the idea itself. Beating a two-year-old implementation of a living research line is the polite version of a strawman, and the line's authors are in the reviewer pool.
[Sweep freshness] newest .bib entry vs deadline: <gap>; intervening cycles covered: CVPR/ECCV/ICCV
[Nearest neighbors] <paper → mechanism delta → consequence> ×2-3
[Concurrent notes] <preprints + dates + handling>
[Self-reference] third person clean · repo uncited · no citation holes
[Attribution check] entries verified against dblp/CVF: <n>
[Gap sentence] <the one-sentence unsolved thing the paper solves>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in ICCV-Skills/skills/iccv-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Iccv Related Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iccv Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Neurips Related Workfranklee16/academic-research-skills | 223 | 1 repos | ~491 | Automated safety check: Pass | None | |
| Ijcai Related Workfranklee16/academic-research-skills | 223 | 1 repos | ~427 | Automated safety check: Pass | None | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Systematic Literature Review Builderbytedance/deer-flow | 84k | 2 repos | ~4.3k | Automated safety check: Pass | MIT |
franklee16/academic-research-skills
A skill your agent uses when positioning a NeurIPS submission against current-cycle ML literature, contemporaneous work, preprints, neighboring conferences, and the exact technical delta from prior…
franklee16/academic-research-skills
A skill your agent uses when positioning an IJCAI or IJCAI-ECAI submission against archival AI literature, arXiv preprints, workshop papers, prior rejected versions, dual-submission rules, shortened…
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
bytedance/deer-flow
Searches arXiv across many papers on one topic, extracts each paper's methodology and findings in parallel, and synthesizes a cited literature review.
XiaomiMiMo/MiMo-Code
Searches arXiv, fetches metadata, generates BibTeX, downloads PDFs and finds citations and related papers using a bundled Python script.
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Categories
A skill your agent uses 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…. Iccv Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Iccv Related Work fits situations like: 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.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a claude-code`. Or copy the skill folder (ICCV-Skills/skills/iccv-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iccv-related-work in your project. Claude Code loads it when a task matches its description.
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a codex`. Or copy the skill folder (ICCV-Skills/skills/iccv-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iccv-related-work in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-related-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iccv-related-work, .gemini/skills/iccv-related-work, .github/skills/iccv-related-work and .opencode/skills/iccv-related-work in your project.
SKILL.md names no scripts, command-line tools or credentials: Iccv Related Work is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Iccv Related Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Iccv Related Work: Neurips Related Work (franklee16/academic-research-skills, 223 stars), Ijcai Related Work (franklee16/academic-research-skills, 223 stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars) and Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
