Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
A skill your agent uses when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the…
MITAuto-check passed
Install Wacv Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-submission --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-submission .claude/skills/wacv-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-submission into .claude/skills/wacv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-submission --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-submission .agents/skills/wacv-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-submission into .agents/skills/wacv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-submission --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-submission .cursor/skills/wacv-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-submission into .cursor/skills/wacv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills wacv-submission --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-submission .gemini/skills/wacv-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-submission into .gemini/skills/wacv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/wacv-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-submission into .github/skills/wacv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-submission", 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-submission -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-submission --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-submission .opencode/skills/wacv-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/WACV-Skills/skills/wacv-submission into .opencode/skills/wacv-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wacv-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 683 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the…
- Works in 2 steps: Round 1 or Round 2. They are different… → Applications or Algorithms track. The…
- Auditing a WACV submission before an OpenReview round deadline
- SKILL.md covers First decision: which round,…, Format discipline, WACV flavor, Anonymity and the anonymized… and Desk-reject and triage table, plus 3 more sections
- Calls pdftotext
What it does
Wacv Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.
Its SKILL.md is about 1.5k 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
- Auditing a WACV submission before an OpenReview round deadline
- Covering the Round 1 vs Round 2 choice
- The Applications vs Algorithms track field
- The 8-page-including-figures limit
Example prompts
- “/wacv-submission”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Round 1 or Round 2. They are different OpenReview groups. Round 1 (reported paper
- Applications or Algorithms track. The two tracks are reviewed against different
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 683 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). 683 words, ~1,463 tokens.
Download SKILL.mdSave it as
.claude/skills/wacv-submission/SKILL.md (or your agent's skills folder).- name
- wacv-submission
- description
- Use when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.
WACV Submission
Run this audit in the two weeks before a WACV round deadline. The specifics below are the WACV 2026/2027 cycles as read on 2026-07-09; chairs rewrite details each edition, and WACV uniquely runs two rounds, so reopen the current Author Guidelines, Dates page, and the correct OpenReview round group at wacv.thecvf.com before acting on any number here.
First decision: which round, which track
Two fields on the OpenReview form change everything downstream, and both are chosen before you write a word of the audit:
- Round 1 or Round 2. They are different OpenReview groups. Round 1 (reported paper deadline June 26, 2026 for WACV 2027) gives you a rebuttal and the Revise-and-Resubmit safety net — a paper that is close but not done can be invited back rather than killed. Round 2 (reported August 28, 2026) is Accept/Reject with no rebuttal; it is for polished work and for revised Round 1 papers. Submitting a borderline paper straight to Round 2 throws away the mechanism WACV built to help it.
- Applications or Algorithms track. The two tracks are reviewed against different criteria (systems-level innovation and comparative assessment vs algorithmic novelty and matched-baseline evaluation). Pick the track where the contribution is stronger, and make the first page argue for that lens — a mis-tracked paper draws a reviewer asking the wrong question, which is a fast route to Revise and Resubmit.
Format discipline, WACV flavor
The cap is 8 pages including figures and tables, in the WACV style, with extra pages for cited references only. That "including figures" clause makes a qualitative grid or a result table a page-budget line item, not a decoration. Build from the current WACV author kit unmodified; treat any style-file edit, margin nudge, or font substitution as a desk-reject trigger. Every author needs a valid OpenReview profile by the round deadline — an incomplete profile on the advisor added late or the intern who wrote one module is desk-reject exposure for the whole paper.
Anonymity and the anonymized supplement
WACV is double-blind: reviewers should not be able to infer authorship "beyond reasonable doubt" from the paper or the supplement. Anonymize acknowledgements (no co-workers, grant IDs), PDF metadata, self-citations (third person), filenames, and any movie titles or overlays in supplementary videos; do not link to sites that identify the authors. A technical report / arXiv preprint is handled under the current prior-publication rule — check it rather than assuming, and never rely on an external link to carry review content.
# Mechanical sweep on the final build, ten minutes before upload
pdftotext paper.pdf - | grep -nEi 'github\.com|drive\.google|project page|our (prior|previous) work' | head
pdfinfo paper.pdf | grep -Ei 'author|creator|producer' # identity in metadata
grep -rn 'vspace\|\\addtolength\|geometry' main.tex # style-tampering tells
pdftotext paper.pdf - | awk 'END{print NR" lines extracted"}' # sanity: text present, not rasterShow full SKILL.md (272 more words)Show less
Desk-reject and triage table
| Finding | Severity at WACV | Recoverable? |
|---|---|---|
| Coauthor without a valid OpenReview profile at the round deadline | Desk reject | Only before that deadline |
| Page 9 contains anything besides references | Rejected without review | Only before the round deadline |
| Style file modified / margins compressed | Rejected without review | Fix and rebuild |
| Identity leak (metadata, acknowledgements, linked repo, video overlay) | Desk reject | Sweep before upload |
| Wrong track for the contribution | Not a reject, but Revise-and-Resubmit risk | Re-frame first page before deadline |
| Same work under review elsewhere in violation of the dual-submission rule | Administrative rejection | Withdraw one venue first |
| Borderline paper sent straight to Round 2 | No rebuttal, no R&R net | Prefer Round 1 next time |
Final-week sequence
- Confirm the round and track fields; they set every other decision.
- Freeze the 8-page body; late edits go to the supplement queue, not the main PDF.
- Rebuild from a clean checkout of the WACV author kit; verify no local style patches leaked in and pages 9+ are references only.
- Run the mechanical sweep above; treat every hit as a blocker.
- Confirm every coauthor's OpenReview profile is valid, and that the OpenReview abstract matches the PDF abstract verbatim.
- Upload, re-download, and read your own submission cold — including checking figures at print zoom, since applications reviewers judge qualitative results visually.
Reverify each cycle
- Both round deadlines and whether the two-round model still holds for the target year.
- The page cap and whether references-only overflow still applies.
- The track definitions and review criteria (Applications vs Algorithms).
- The prior-publication / arXiv rule and the dual-submission window.
- Supplementary size/format caps (not fetchable for 2026 — 待核实).
Output format
[WACV submission] ready / blocked / at-risk
[Round] R1 (rebuttal + R&R net) / R2 (Accept-Reject, no rebuttal) — chosen: <one>
[Track] Applications / Algorithms — first page argues for it: yes/no
[Profiles] all coauthors valid on OpenReview: yes/no
[Format] pages used (of 8 incl. figures/tables) · refs-only overflow ok
[Anonymity/links] clean / violations: <list>
[Fix queue] <ordered blockers>© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Wacv Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Production Auditaffaan-m/ECC | 277k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Aims Auditalirezarezvani/claude-skills | 28k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Geo Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Notes | MIT | |
| OmniRoute Audit and Policy CLIdiegosouzapw/OmniRoute | 75k | — | ~733 | Automated safety check: Pass | MIT | |
| Audit Preparationsickn33/agentic-awesome-skills | 47k | 1 repos | ~5.3k | Automated safety check: Pass | MIT |
Similar skills
Aims Audit
alirezarezvani/claude-skills
/cs:aims-audit <scope — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation.
Geo Audit
sickn33/agentic-awesome-skills
Full website GEO+SEO audit with parallel subagent delegation.
OmniRoute Audit and Policy CLI
diegosouzapw/OmniRoute
Command reference for omniroute's audit, logs, policy and telemetry commands: search and export audit trails, manage access policies and review request history for compliance work.
Audit Preparation
sickn33/agentic-awesome-skills
Audit preparation register: required document, period covered, request and receipt dates, preparer and reviewer, auditor queries and adjustments.
Qms Audit Expert
davila7/claude-code-templates
Senior QMS Audit Expert for internal and external quality management system auditing.
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 Submission
What does Wacv Submission do?
A skill your agent uses when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the…. Wacv Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing a WACV submission before an OpenReview round deadline, covering the Round 1 vs Round 2 choice, the Applications vs Algorithms track field, the 8-page-including-figures limit, double-blind anonymity and OpenReview-profile requirements, the anonymized supplement, dual submission, and desk-reject triage.
When should I use Wacv Submission?
Wacv Submission fits situations like: auditing a WACV submission before an OpenReview round deadline; covering the Round 1 vs Round 2 choice; the Applications vs Algorithms track field; the 8-page-including-figures limit.
How do I install Wacv Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-submission -a claude-code`. Or copy the skill folder (WACV-Skills/skills/wacv-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/wacv-submission in your project. Claude Code loads it when a task matches its description.
How do I install Wacv Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill wacv-submission -a codex`. Or copy the skill folder (WACV-Skills/skills/wacv-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/wacv-submission in your project. Codex loads it when a task matches its description.
Can I use Wacv Submission 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-submission -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-submission, .gemini/skills/wacv-submission, .github/skills/wacv-submission and .opencode/skills/wacv-submission in your project.
What does Wacv Submission need to run?
Going by SKILL.md and its folder, Wacv Submission needs the command-line tools its instructions call (pdftotext).
Does Wacv Submission 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 Submission 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 Submission use?
Wacv Submission 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 Submission use?
About 1.5k tokens (SKILL.md is roughly 5.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 Submission?
Skills that share tags, products or a category with Wacv Submission: Production Audit (affaan-m/ECC, 277k stars), Aims Audit (alirezarezvani/claude-skills, 28k stars), Geo Audit (sickn33/agentic-awesome-skills, 47k stars) and OmniRoute Audit and Policy CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wacv Submission?
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.