Individual skill
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.
CAV-Skills/skills/cav-writing-style/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,400
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- finance Derived category
- writing Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 5,493 bytes
Read excerpt
# 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