Ito Compute
affaan-m/ECC
Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, revoke device credentials, and run explicitly gated node qualification through the separately…
A skill your agent uses when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal…
MITAuto-check passed
Install Cav Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-workflow --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/CAV-Skills/skills/cav-workflow .claude/skills/cav-workflow && 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 "cav-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-workflow into .claude/skills/cav-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-workflow", 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/CAV-Skills/skills/cav-workflowType 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 cav-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-workflow --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/CAV-Skills/skills/cav-workflow .agents/skills/cav-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cav-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-workflow into .agents/skills/cav-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-workflow", 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 cav-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-workflow --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/CAV-Skills/skills/cav-workflow .cursor/skills/cav-workflow && 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 "cav-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-workflow into .cursor/skills/cav-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-workflow", 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 CAV-Skills/skills/cav-workflow--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 cav-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills cav-workflow --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/CAV-Skills/skills/cav-workflow .gemini/skills/cav-workflow && 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 "cav-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-workflow into .gemini/skills/cav-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-workflow", 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 cav-workflowInstalls 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 cav-workflow -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/CAV-Skills/skills/cav-workflow .github/skills/cav-workflow && 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 "cav-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-workflow into .github/skills/cav-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-workflow", 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 cav-workflow -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 cav-workflow --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/CAV-Skills/skills/cav-workflow .opencode/skills/cav-workflow && 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 "cav-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CAV-Skills/skills/cav-workflow into .opencode/skills/cav-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cav-workflow", 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
cav-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 653 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal…
- Planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission
- SKILL.md covers Milestones, Backward plan from the…, The two-stage cycle: plan for… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The two-stage review with early reject and rebuttal
What it does
Cav Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.
Its SKILL.md is about 1.4k 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
- Planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission
- The two-stage review with early reject and rebuttal
- Artifact evaluation by the AEC
- The LNCS open-access camera-ready
Example prompts
- “/cav-workflow”
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
Cav Workflow loads about 1.4k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 653 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). 653 words, ~1,372 tokens.
Download SKILL.mdSave it as
.claude/skills/cav-workflow/SKILL.md (or your agent's skills folder).- name
- cav-workflow
- description
- Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.
CAV Workflow
Use this as the project-management skill for a CAV submission. Replace every date with the current official timetable and work backward from the AoE paper deadline. CAV publishes open access in Springer LNCS, reviews in two stages (an early-reject filter, then a rebuttal), and runs an optional artifact evaluation after notification — plan for all three, not just accept/reject.
CAV is a conference with no standing editor-in-chief; the rotating leadership is the per-edition Program Chairs and Steering Committee. For CAV 2026 the Program Chairs are Anthony W. Lin, Eva Darulova, and Philipp Rümmer (verified 2026-07-09), and the venue is Lisbon, part of FLoC 2026. Chairs rotate yearly; re-check the organization page rather than carrying a name forward.
Milestones
- Venue + category fit: confirm CAV over TACAS/FMCAD/VMCAI and pick the category (Regular /
Tool / Application / Industrial) (
cav-topic-selection). - Evidence lock: freeze the theorem/algorithm, the benchmark set (revision pinned), the baseline tools and versions, the resource limits, and the artifact contents.
- Submission: upload the LNCS-formatted PDF in the right category, anonymized if Regular or Application, with the artifact-intent declaration set (CAV 2026: 28 Jan 2026 AoE).
- Stage-1 filter: each paper gets two reviews; weak papers are rejected early (tentative first-round outcome ~4 Mar 2026).
- Rebuttal: papers passing stage 1 get two more reviews and an author-response window (CAV 2026: 30 Mar - 2 Apr 2026).
- Notification: accept/reject (CAV 2026: 17 Apr 2026); archive all reviews and versions.
- Artifact evaluation (optional): register and submit to the AEC on its own deadline (CAV 2026 artifact registration: 22 Apr 2026), pursuing Available / Functional / Reusable badges.
- Camera-ready: prepare the LNCS open-access final version and complete Springer metadata and rights; present at the conference (CAV 2026: 26-29 Jul 2026, Lisbon / FLoC).
Backward plan from the submission deadline
| Weeks out (heuristic) | Verification-paper milestone |
|---|---|
| 10+ | Technique/algorithm fixed; the soundness/completeness statement drafted |
| 8 | Tool implemented and stable; benchmark set and baseline tools/versions chosen and pinned |
| 6 | Full evaluation run under fixed resource limits; per-instance data and logs archived |
| 4 | Full draft in llncs; proofs complete (in body or clearly-marked appendix); artifact assembled |
| 3 | Internal mock review by a verification-literate reader; differential/soundness cross-check done |
| 2 | Scope and limits sharpened; related-work delta tightened; page limit met |
| 1 | Anonymity sweep on PDF and artifact (Regular/Application); artifact-intent decided |
| 0 | Upload in the correct category via the live portal; re-download to confirm |
These offsets are planning heuristics only — anchor every one to the current Important Dates page, never to a previous cycle's calendar.
Show full SKILL.md (248 more words)Show less
The two-stage cycle: plan for the early reject
CAV's stage-1 filter means a paper can be rejected before the rebuttal ever happens. Two planning consequences:
- The first two reviews must be able to defend the paper on their own. A contribution that only becomes convincing after the rebuttal may never reach stage 2. Make the soundness and the headline benchmark result legible in the first read.
- Missing the annual deadline costs roughly a year at CAV. A sibling flagship (TACAS in spring,
FMCAD, VMCAI) may have a nearer date — factor that into routing rather than idling
(
cav-topic-selection).
Failure modes by stage
- Tool still unstable at week 6 forces a rushed evaluation nobody audited — the classic reproducibility/soundness doubt in the making.
- Benchmarks or baselines unpinned means the comparison cannot be reproduced and the reviewer discounts the numbers.
- Leaving anonymization to the final week (Regular/Application) is how a solver name or a benchmark path leaks identity under double-blind review.
- Treating stage 1 as a formality and saving the strongest framing for the rebuttal forfeits the paper before the rebuttal exists.
- Assuming artifact evaluation is required — it is optional and non-conditional at CAV; plan it, but do not block the camera-ready on it.
Coordination notes
- Assign one owner for the artifact (benchmarks, versions, seeds, resource limits) and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, the artifact, and (later) the rebuttal — a stage-2 review and any camera-ready must quote them precisely.
Output format
[Current stage] idea / evidence / writing / submitted / stage-1 / rebuttal / accepted / artifact
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <category / page limit / anonymity / benchmarks+baselines / soundness / artifact>
[Owner map] <task -> person or role>© 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 CAV-Skills/skills/cav-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Cav Workflow 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 |
|---|---|---|---|---|---|---|
| Cav Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Ito Computeaffaan-m/ECC | 275k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Senior Computer Visiondavila7/claude-code-templates | 32k | 3 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Senior Computer Visionalirezarezvani/claude-skills | 28k | 2 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 98k | 1 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GCP Computesickn33/agentic-awesome-skills | 47k | 2 repos | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
Senior Computer Vision
davila7/claude-code-templates
World-class computer vision skill for image/video processing, object detection, segmentation, and visual AI systems.
Senior Computer Vision
alirezarezvani/claude-skills
Computer vision engineering skill for object detection, image segmentation, and visual AI systems.
Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
GCP Compute
sickn33/agentic-awesome-skills
Manage Compute Engine instances and instance templates. An agent skill from sickn33/agentic-awesome-skills.
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
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 Cav Workflow
What does Cav Workflow do?
A skill your agent uses when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal…. Cav Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.
When should I use Cav Workflow?
Cav Workflow fits situations like: planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission; the two-stage review with early reject and rebuttal; artifact evaluation by the AEC; the LNCS open-access camera-ready.
How do I install Cav Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-workflow -a claude-code`. Or copy the skill folder (CAV-Skills/skills/cav-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cav-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Cav Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-workflow -a codex`. Or copy the skill folder (CAV-Skills/skills/cav-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cav-workflow in your project. Codex loads it when a task matches its description.
Can I use Cav Workflow 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 cav-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cav-workflow, .gemini/skills/cav-workflow, .github/skills/cav-workflow and .opencode/skills/cav-workflow in your project.
What does Cav Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Cav Workflow is instructions for the agent only.
Does Cav Workflow 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 Cav Workflow 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 Cav Workflow use?
Cav Workflow 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 Cav Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.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 Cav Workflow?
Skills that share tags, products or a category with Cav Workflow: Ito Compute (affaan-m/ECC, 275k stars), Senior Computer Vision (davila7/claude-code-templates, 32k stars), Senior Computer Vision (alirezarezvani/claude-skills, 28k stars) and Project Timeline Report (thedotmack/claude-mem, 98k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Cav Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.