cav-related-work
Use when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR, TOCL, STTT), writing delta-first contrast rather than a citation catalog, crediting the right benchmark and tool lineages, keeping self-citations double-anonymous for the anonymized categories, and handling concurrent and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-related-work --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 Related Work Use this to audit novelty and eligibility. CAV reviewers are close to the verification literature and expect to see where your paper sits relative to the nearest prior technique or tool — stated as a **delta**, not a list. Reopen the current CFP for dual-submission, anonymity, and prior-publication rules before advising authors. ## Positioning checks - **Separate the verification novelty from the engineering effort.** What is new: an algorithm, a decision procedure, an abstraction, a soundness result, a tool capability, or a benchmark regime nobody had covered? - **Cover the verification lanes.** CAV reviewers expect the flagship venues, the tool ecosystems, and the journals — not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware. - **Write delta-first.** Each closely related paper gets one sentence naming what it did and one naming what you do differently — a technical contrast (what their method cannot do that yours can), not a summary. - **Credit tool and benchmark lineages.** If you extend or compare against a solver/model checker or use a standard benchmark set, cite the tool paper and the b
- Positioning checks
- Verification literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the cav-related-work skill do?
Use when positioning a CAV (Computer Aided Verification) submission against the verification literature across CAV, TACAS, FMCAD, VMCAI, POPL/PLDI, and the journals (FMSD, JAR, TOCL, STTT), writing delta-first contrast rather than a citation catalog, crediting the right benchmark and tool lineages, keeping self-citations double-anonymous for the anonymized categories, and handling concurrent and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-related-work --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.