cav-writing-style
Use when revising a CAV (Computer Aided Verification) paper for a precise verification contribution on the first page, an explicit soundness/completeness statement, theorem-and-proof discipline in the LNCS page budget, fair benchmark claims, honest scope and limits, and double-blind wording for the anonymized categories.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-writing-style --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 Writing Style Use this when revising the main paper. CAV papers are Springer LNCS chapters read by verification researchers, so they need a **precise verification contribution stated on the first page** and a **formal guarantee** a reviewer can check. The failure this skill prevents is a technically fine paper that reads like a systems demo or a heuristic with a benchmark table but no stated property. ## Revision rules - **Lead with the verification contribution and its guarantee:** the problem (what property, of what system), why current methods fall short, the contribution (technique and/or tool), **what is formally guaranteed** (soundness, completeness, an equisatisfiability/refinement claim), the benchmark evidence, and the scope. - **State the formal claim precisely.** Name the property, the assumptions, and the theorem. A paper whose "contribution" is only "faster on benchmarks" with no guarantee reads as a tool note, not a Regular Paper. - **Give proofs their place.** Key proofs go in the body; long proofs may go to a clearly-marked appendix — but reviewers are not obliged to read appendices, so the proof *idea* must be in the body (see `cav-supplementary`). - **Make b
- Revision rules
- Verification-paper skeleton
- Sentence-level rewrites
- Correctness-and-scope discipline
- Vignette: compressing a technique-plus-tool paper
- Output format
What does the cav-writing-style skill do?
Use when revising a CAV (Computer Aided Verification) paper for a precise verification contribution on the first page, an explicit soundness/completeness statement, theorem-and-proof discipline in the LNCS page budget, fair benchmark claims, honest scope and limits, and double-blind wording for the anonymized categories.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-writing-style --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.