Agent skill · Documentation

wacv-related-work

Use when writing or auditing a WACV related-work section, covering how to position an applications or algorithms contribution against fast-moving vision literature, sibling-venue (CVPR/ICCV/ECCV) and arXiv concurrency, application-domain literature, double-blind self-citation, and verifying that cited "WACV papers" are actually WACV papers.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-related-work --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: WACV-Skills/skills/wacv-related-work/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# WACV Related Work Use this to position a WACV paper so reviewers see the gap it fills, not a wall of citations. WACV's applications identity adds a shelf most vision venues underweight — the **domain literature** — and its two-round model means a thin related-work section is a predictable revision request. Facts are the WACV 2026/2027 cycles as read on 2026-07-09. ## The shelves to cover | Shelf | What it establishes | Failure if missing | |---|---|---| | Vision method lineage | Where your method sits among CV approaches | Reviewer thinks you reinvented a known method | | Sibling-venue recent work | Awareness of CVPR/ICCV/ECCV state of the art | Looks unaware of the field's frontier | | arXiv / concurrent work | Honest handling of near-simultaneous results | Accused of ignoring obvious concurrency | | **Application-domain literature** | That you understand the real problem (agriculture, medical, robotics) | Applications reviewer sees a naive domain model | | Your own prior work (anonymized) | Continuity without breaking double-blind | Identity leak or apparent self-plagiarism | The domain shelf is what separates a strong WACV applications paper from a generic method with a domain

What's inside
Steps it walks through
  1. The shelves to cover
  2. Positioning, not enumeration
  3. Concurrency at arXiv speed
  4. Double-blind self-citation
  5. Verify the venue of every "WACV" citation
  6. Reverify each cycle
  7. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the wacv-related-work skill do?

Use when writing or auditing a WACV related-work section, covering how to position an applications or algorithms contribution against fast-moving vision literature, sibling-venue (CVPR/ICCV/ECCV) and arXiv concurrency, application-domain literature, double-blind self-citation, and verifying that cited "WACV papers" are actually WACV papers.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-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 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.

Keep going