cav-artifact-evaluation
Use when packaging a CAV (Computer Aided Verification) artifact for the Artifact Evaluation Committee (AEC), covering the three badges (Available / Functional / Reusable), the smoke-test and full-review phases, ≥2 AEC reviewers per artifact, DOI-issuing archives, verification-tool packaging (solvers, benchmarks, seeds, resource limits, proof witnesses), and the fact that AE is invited, post-notification, and non-conditional.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-artifact-evaluation --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 Artifact Evaluation Use this for the artifact track. CAV artifact evaluation is run by a dedicated **Artifact Evaluation Committee (AEC)**, is **invited but optional** after notification, and — importantly — **final paper acceptance is not conditional** on it. Authors declare **artifact intent at submission time**; the actual AEC submission comes after acceptance, on the artifact track's own deadline (CAV 2026 artifact registration: 22 Apr 2026). Two things to internalize: badges are earned by AEC members actually running your package, and for anonymized paper categories the review-time material and the AEC artifact are handled differently (the AEC artifact is post-notification, so de-anonymization is fine). ## The three badges (verify the current set and names) | Badge | What it certifies | What earns it | |---|---|---| | Available | The artifact is permanently, publicly retrievable | Deposit in a **DOI-issuing archival repository** (Zenodo, figshare, Software Heritage) | | Functional | The artifact is documented, consistent, complete, and exercisable | A clean-machine install, a working run, and documented expected outputs | | Reusable | Quality significantly exceeds Functi
- The three badges (verify the current set and names)
- How the AEC evaluates (two phases, ≥2 reviewers)
- What AEC reviewers open first (verification-specific)
- Packaging plan for a verification artifact
- Worked vignette: packaging an SMT-solver + benchmark study
- Calibration
- Output format
What does the cav-artifact-evaluation skill do?
Use when packaging a CAV (Computer Aided Verification) artifact for the Artifact Evaluation Committee (AEC), covering the three badges (Available / Functional / Reusable), the smoke-test and full-review phases, ≥2 AEC reviewers per artifact, DOI-issuing archives, verification-tool packaging (solvers, benchmarks, seeds, resource limits, proof witnesses), and the fact that AE is invited, post-notification, and non-conditional.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-artifact-evaluation --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.