Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
A skill your agent uses when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the…
MITAuto-check passed
Install Wacv Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-topic-selection --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/WACV-Skills/skills/wacv-topic-selection .claude/skills/wacv-topic-selection && 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 "wacv-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-topic-selection into .claude/skills/wacv-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-topic-selection", 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/WACV-Skills/skills/wacv-topic-selectionType 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 wacv-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-topic-selection --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/WACV-Skills/skills/wacv-topic-selection .agents/skills/wacv-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wacv-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-topic-selection into .agents/skills/wacv-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-topic-selection", 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 wacv-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-topic-selection --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/WACV-Skills/skills/wacv-topic-selection .cursor/skills/wacv-topic-selection && 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 "wacv-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-topic-selection into .cursor/skills/wacv-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-topic-selection", 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 WACV-Skills/skills/wacv-topic-selection--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 wacv-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-topic-selection --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/WACV-Skills/skills/wacv-topic-selection .gemini/skills/wacv-topic-selection && 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 "wacv-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-topic-selection into .gemini/skills/wacv-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-topic-selection", 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 wacv-topic-selectionInstalls 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 wacv-topic-selection -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/WACV-Skills/skills/wacv-topic-selection .github/skills/wacv-topic-selection && 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 "wacv-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-topic-selection into .github/skills/wacv-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-topic-selection", 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 wacv-topic-selection -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 wacv-topic-selection --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/WACV-Skills/skills/wacv-topic-selection .opencode/skills/wacv-topic-selection && 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 "wacv-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-topic-selection into .opencode/skills/wacv-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-topic-selection", 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.
Facts
- Skill name
wacv-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 506 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the…
- Deciding whether a project belongs at WACV
- SKILL.md covers The core question, Routing across the CVF…, Choosing the track and A quick self-test, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Should route elsewhere
What it does
Wacv Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the Applications-vs-Algorithms track choice, whether the two-round winter timing fits your schedule, and routing to CVPR, ICCV, ECCV, 3DV, or a journal.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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.
When your agent uses it
- Deciding whether a project belongs at WACV
- Should route elsewhere
- Covering WACVs applications-first identity within the CVFs CVPR/ICCV/ECCV/WACV calendar
- The Applications-vs-Algorithms track choice
Example prompts
- “s applications-first identity within the CVF”
- “/wacv-topic-selection”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wacv Topic Selection loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 506 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 506 words, ~1,131 tokens.
Download SKILL.mdSave it as
.claude/skills/wacv-topic-selection/SKILL.md (or your agent's skills folder).- name
- wacv-topic-selection
- description
- Use when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the Applications-vs-Algorithms track choice, whether the two-round winter timing fits your schedule, and routing to CVPR, ICCV, ECCV, 3DV, or a journal.
WACV Topic Selection
WACV is the applications-first winter member of the Computer Vision Foundation's four-venue calendar (CVPR in June, ICCV/ECCV alternating in autumn, WACV in winter). This skill decides whether to send a paper here — and, if so, which track — before other skills decide how. Facts are the WACV 2026/2027 cycles as read on 2026-07-09.
The core question
Ask two things in order. First: is the contribution about applying computer vision to a real problem, or advancing vision method for its own sake? WACV's name — Applications of Computer Vision — is a genuine editorial stance, and its Applications track exists to review systems that work under real constraints. Second: does the winter, two-round calendar fit your timeline better than waiting for a single-deadline sibling? A paper that is nearly ready in mid-summer can enter WACV Round 1 and, if close, be invited to revise — rather than sitting until the next CVPR cycle.
Routing across the CVF calendar (from WACV's seat)
| You have… | WACV-shaped if… | Route elsewhere if… |
|---|---|---|
| A vision system for a real domain (agriculture, medical, retail, robotics) under real constraints | The constraint (power, data scarcity, in-the-wild robustness) is the contribution | It is a generic method with an arbitrary demo domain → CVPR/ICCV/ECCV |
| A new architecture / algorithm | It advances a vision mechanism and you want the winter slot and the R&R net | It is a field-defining method aimed at the largest audience → CVPR |
| A benchmark / re-evaluation of a deployed task | It corrects how a real task is measured or constrained | It is a broad foundation-model benchmark → a larger venue |
| A 3D / geometry contribution | It is applied and constraint-driven | It is core 3D reconstruction method → 3DV or CVPR |
| A theory / learning result with a vision demo | (rarely WACV) | The claim is statistical/learning-theoretic → NeurIPS/ICML/AISTATS |
WACV is not a "CVPR reject bin." It is a real venue with its own applications identity, a respectable acceptance profile, and a review model designed to improve papers across two rounds rather than gate them once.
Show full SKILL.md (179 more words)Show less
Choosing the track
Once WACV is the answer, the track is the next decision, and it changes how you write the first page:
- Applications track — reviewed on systems-level innovation, novelty of the application domain, and comparative assessment under real-world constraints (low-power inference, data scarcity, robustness in the wild). Choose this when the value is that the system works under a named constraint, not that the math is new.
- Algorithms track — reviewed on algorithmic novelty and quantified evaluation against current alternatives. Choose this when you introduce a genuinely new method or architecture and can show matched-baseline wins.
Authors pick one primary track. If a paper seems to fit both, choose the track where the contribution is stronger, and frame the first page to argue for that lens — a mis-tracked paper draws the wrong review question and heads for Revise and Resubmit.
A quick self-test
Is the deployment constraint the point? yes → Applications track, WACV strong
Is a new vision mechanism the point? yes → Algorithms track (WACV) or CVPR/ICCV/ECCV
Is vision only the demo for a learning claim? yes → route to NeurIPS/ICML/AISTATS
Do you want a revision path if you're close? yes → WACV Round 1 fits
Is the claim about a non-vision modality's math? yes → not WACVReverify each cycle
- The two-track structure and each track's review criteria.
- WACV's place and timing in the CVF calendar and the two-round dates.
- Whether the winter cycle's deadlines actually beat your next sibling-venue option.
Output format
[Verdict] WACV / route to <CVPR|ICCV|ECCV|3DV|journal|other>
[Why] <one line: applications-under-constraint vs method-for-its-own-sake>
[Track if WACV] Applications / Algorithms — because <criterion match>
[Timing] winter two-round fits: yes/no
[Risk] <the reviewer question this framing must pre-empt>© 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
Files
Just SKILL.md in WACV-Skills/skills/wacv-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wacv Topic Selection 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 |
|---|---|---|---|---|---|---|
| Wacv Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| TopicsZimoLiao/scholaraio | 577 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Bestblogs Topicginobefun/BestBlogs | 4k | — | ~670 | Automated safety check: Pass | None | |
| Zsxq Topicitwanger/toBeBetterJavaer | 18k | — | ~564 | Automated safety check: Pass | None | |
| Pubmed Topic Recommendaipoch/medical-research-skills | 2k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
Zsxq Topic
itwanger/toBeBetterJavaer
知识星球主题管理：搜索主题、查看主题详情、发布帖子、编辑主题、发表评论、回复某条评论（楼中楼）、回答提问、删除主题；通过 api call 查看主题评论列表、设置精华、设置标签、查看自己提的问题与已回答记录。当用户需要查找内容、发帖、编辑主题、评论、回复评论、回答问题、删除主题、查看主题评论、查看自己的提问记录、或管理主题精华和标签时使用。
Pubmed Topic Recommend
aipoch/medical-research-skills
Generate ~5 actionable research topic recommendations by querying PubMed E-utilities; use when a user provides a research direction/constraints and needs evidence-backed topic ideas quickly.
TiXL UI Topic Doc Writer
tixl3d/tixl
Fills in empty embedded help text for TiXL's UI topics by distilling the maintainer's own video explanations into short, user-facing doc entries.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
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…
Aaag Literature Positioning
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…
Aaag Rebuttal
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…
Aaag Research Design
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…
Aaag Review Process
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…
Aaag Submission
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…
Questions about Wacv Topic Selection
What does Wacv Topic Selection do?
A skill your agent uses when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the…. Wacv Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a project belongs at WACV or should route elsewhere, covering WACV's applications-first identity within the CVF's CVPR/ICCV/ECCV/WACV calendar, the Applications-vs-Algorithms track choice, whether the two-round winter timing fits your schedule, and routing to CVPR, ICCV, ECCV, 3DV, or a journal.
When should I use Wacv Topic Selection?
Wacv Topic Selection fits situations like: deciding whether a project belongs at WACV; should route elsewhere; covering WACVs applications-first identity within the CVFs CVPR/ICCV/ECCV/WACV calendar; the Applications-vs-Algorithms track choice.
How do I install Wacv Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-topic-selection -a claude-code`. Or copy the skill folder (WACV-Skills/skills/wacv-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wacv-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Wacv Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-topic-selection -a codex`. Or copy the skill folder (WACV-Skills/skills/wacv-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wacv-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Wacv Topic Selection in Cursor, Gemini CLI or GitHub Copilot?
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 wacv-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wacv-topic-selection, .gemini/skills/wacv-topic-selection, .github/skills/wacv-topic-selection and .opencode/skills/wacv-topic-selection in your project.
What does Wacv Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Wacv Topic Selection is instructions for the agent only.
Does Wacv Topic Selection access the network?
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.
Is Wacv Topic Selection safe to install?
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.
What licence does Wacv Topic Selection use?
Wacv Topic Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wacv Topic Selection use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wacv Topic Selection?
Skills that share tags, products or a category with Wacv Topic Selection: Topics (ZimoLiao/scholaraio, 577 stars), Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Bestblogs Topic (ginobefun/BestBlogs, 4k stars) and Zsxq Topic (itwanger/toBeBetterJavaer, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wacv Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.