cav-submission
Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# CAV Submission Run this audit before uploading to the CAV submission portal. CAV research papers are published open access as **Springer LNCS chapters**, and the submission is judged by a two-stage review, so the category you pick, the LNCS format, and the anonymization rule for that category all have to be right before the deadline. Every number below was read from the CAV 2026 Call for Papers on 2026-07-09 via search renderings of the `i-cav.org` URLs (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live CFP first. ## Pick the right category first CAV 2026 solicits **four** categories, and the category sets both the page limit and the anonymity rule: | Category | Page limit (LNCS, excl. refs + appendix) | Anonymized? | Fits | |---|---|---|---| | Regular Paper | 18 pages | **Yes** (double-blind) | A new technique/algorithm with a formal contribution | | Short Tool Paper | 10 pages | **No** | A usable, downloadable verification tool on standard benchmarks | | Short Application Paper | 10 pages | **Yes** (double-blind) | Applying verification to a concrete problem/system | | Industrial Experience Report & Case Study | 10 pages | **No** |
- Pick the right category first
- Format and page budget
- Double-blind sweep (Regular and Application papers)
- Artifact intent at submission time
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on an anonymized submission PDF and any artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org|our (tool|solver|prover)|acknowledg|grant' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/' | head
What does the cav-submission skill do?
Use when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-submission --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.