Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal…
Install Wacv Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-review-process --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-review-process .claude/skills/wacv-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-review-process into .claude/skills/wacv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-review-process --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-review-process .agents/skills/wacv-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-review-process into .agents/skills/wacv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-review-process --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-review-process .cursor/skills/wacv-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-review-process into .cursor/skills/wacv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-review-process --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-review-process .gemini/skills/wacv-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-review-process into .gemini/skills/wacv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/wacv-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-review-process into .github/skills/wacv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/wacv-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-review-process into .opencode/skills/wacv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 556 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal…
- Reasoning about how WACV decides a paper
- SKILL.md covers The two-round pipeline, Where the rebuttal fits (and…, Confidentiality and conduct and Author leverage, by stage, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the two-round model
What it does
Wacv Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal, the no-rebuttal Round 2, area-chair consolidation, double-blind confidentiality, and where author leverage actually exists across the two rounds.
Its SKILL.md is about 1.2k 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. 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
- Reasoning about how WACV decides a paper
- Covering the two-round model
- The Round 1 Accept / Revise-and-Resubmit / Reject recommendations
- The optional Round 1 rebuttal
Example prompts
- “/wacv-review-process”
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 Review Process loads about 1.2k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 556 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). 556 words, ~1,220 tokens.
Download SKILL.mdSave it as
.claude/skills/wacv-review-process/SKILL.md (or your agent's skills folder).- name
- wacv-review-process
- description
- Use when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal, the no-rebuttal Round 2, area-chair consolidation, double-blind confidentiality, and where author leverage actually exists across the two rounds.
WACV Review Process
Use this to model the machine WACV runs your paper through, so effort lands where it moves a decision. WACV's pipeline is unlike its CVF siblings: it is a two-round, journal-style process with an explicit revision path. Facts below are the WACV 2026/2027 cycles as read on 2026-07-09; reopen the current Reviewer Guidelines and Dates page before relying on a date or rule.
The two-round pipeline
Each Round 1 submission is seen by at least three reviewers; the area chair consolidates the reviews and issues one of three recommendations:
| R1 outcome | What it means | What happens next |
|---|---|---|
| Accept | The paper clears the bar as submitted | Proceeds to camera-ready |
| Revise and Resubmit | Not accepted, but plausibly fixable within the cycle | Invited into Round 2 with reviewer-requested revisions |
| Reject | Concerns too large for a short-timeframe revision | Out for this cycle |
Round 2 then reviews two populations together: the revised R1 (Revise-and-Resubmit) papers and brand-new Round 2 submissions. Round 2 recommendations are Accept or Reject only. The scale of the middle band is the headline fact: in WACV 2025's Round 1, of 1381 submissions, roughly 12% were accepted outright, ~37% rejected, and ~51% invited to revise — most papers live or die in the revision lap, not the first review.
Where the rebuttal fits (and where it doesn't)
- Round 1 has an optional one-page rebuttal. After R1 reviews arrive, authors may file a single-page PDF (rebuttal template in the author kit) to correct factual errors and answer the reviewers before the recommendation is set.
- Round 2 has no rebuttal. For revised R1 papers, your "response" is the revision plus the change summary, not a rebuttal PDF; for new R2 submissions, there is simply no author-response step. Plan accordingly — an R2 paper cannot argue itself out of a weak first submission after the fact.
Show full SKILL.md (254 more words)Show less
Confidentiality and conduct
Reviewing is double-blind: authors do not learn reviewer or AC identities, and reviewers should not be able to infer authorship beyond reasonable doubt. Review content is confidential; do not seek reviewer identities, post reviews, or contact chairs to circumvent the process. Treat the AC as the reader who must reconcile three reviews into one recommendation — clarity aimed at the AC pays off more than point-scoring a single reviewer.
Author leverage, by stage
R1 reviews land → optional one-page rebuttal: fix factual errors, answer the top blocker
R1 = Accept → move to camera-ready (see wacv-camera-ready)
R1 = Revise&Resubmit → the real work: make the reviewer-requested changes, write the change
summary, keep paper and artifact in sync for Round 2
R1 = Reject → harvest the reviews; re-target (see wacv-topic-selection) or rebuild
R2 (revised paper) → no rebuttal; the revision *is* the argument
R2 = Accept/Reject → terminal for the cycleThe highest-leverage moment at WACV is not the rebuttal — it is executing a clean Revise-and-Resubmit. A paper that reads its R1 reviews as a concrete revision spec, makes exactly those changes, and documents them, converts far more often than one that argues.
Reading a recommendation honestly
- A Revise and Resubmit is an invitation, not a soft reject: it means the reviewers believe the gap is closable this cycle. Treat every requested change as load-bearing.
- An Accept at R1 is rare and clean — do not reopen the paper beyond camera-ready fixes.
- A Reject with substantive reviews is still valuable input for a sibling venue or the next cycle; separate "reviewers missed it" (rare) from "the paper did not answer the obvious question" (common).
Reverify each cycle
- Whether the two-round model, the three R1 recommendations, and the R2 Accept/Reject set still hold.
- The Round 1 rebuttal format and length, and the confirmation that Round 2 has none.
- Reviewer count per paper and any reviewer-side LLM or conduct rules.
- The exact R1/R2 review and decision dates (reported for 2027 — reconfirm).
Output format
[Stage] R1 reviews / R1 decision / R2 review / R2 decision
[R1 outcome] Accept / Revise&Resubmit / Reject
[Highest-leverage action now] <rebuttal fix | revision spec | re-target>
[If R&R] reviewer-requested changes enumerated: yes/no
[AC-facing clarity] <the one thing the AC must be able to conclude>© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wacv Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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…
Related
Categories
Questions about Wacv Review Process
What does Wacv Review Process do?
A skill your agent uses when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal…. Wacv Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how WACV decides a paper, covering the two-round model, the Round 1 Accept / Revise-and-Resubmit / Reject recommendations, the optional Round 1 rebuttal, the no-rebuttal Round 2, area-chair consolidation, double-blind confidentiality, and where author leverage actually exists across the two rounds.
When should I use Wacv Review Process?
Wacv Review Process fits situations like: reasoning about how WACV decides a paper; covering the two-round model; the Round 1 Accept / Revise-and-Resubmit / Reject recommendations; the optional Round 1 rebuttal.
How do I install Wacv Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-review-process -a claude-code`. Or copy the skill folder (WACV-Skills/skills/wacv-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wacv-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Wacv Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-review-process -a codex`. Or copy the skill folder (WACV-Skills/skills/wacv-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wacv-review-process in your project. Codex loads it when a task matches its description.
Can I use Wacv Review Process 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-review-process -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-review-process, .gemini/skills/wacv-review-process, .github/skills/wacv-review-process and .opencode/skills/wacv-review-process in your project.
What does Wacv Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Wacv Review Process is instructions for the agent only.
Does Wacv Review Process 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 Review Process 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 Review Process use?
Wacv Review Process 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 Review Process use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Review Process?
Skills that share tags, products or a category with Wacv Review Process: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wacv Review Process?
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.