cav-supplementary
Use when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body, where full proofs and benchmark tables live, and double-anonymous supplementary material for the anonymized categories.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-supplementary --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 Supplementary Use this when assembling CAV supplementary material. The governing rule is strict and specific to CAV's format: a **clearly marked appendix is allowed, but reviewers are not obliged to read it**. So the paper must be **judgeable from the body alone** — anything a reviewer must see to accept lives inside the page limit, and the appendix and artifact only support it. ## What goes where | Content | Body (within the page limit) | Appendix / artifact | |---|---|---| | The problem, the technique, the main theorem | Yes | — | | Proof idea / sketch of the main result | Yes | Full formal proof | | Supporting lemmas | Statement + role | Full proofs | | Headline benchmark comparison + resource limits | Yes | Full per-instance tables | | Soundness/differential-check result | The result + method | The raw logs and witnesses | | Benchmark set + selection | Summary + revision | The full instance list, fetch scripts | | Tool build/run instructions | A pointer | README + scripts (artifact) | | Proof certificates / witnesses | A pointer | The certificates + a checker (artifact) | If a reviewer would need to open the appendix or artifact to know whether the theorem holds or the co
- What goes where
- The page-limit discipline
- Double-anonymous supplementary rules (Regular and Application papers)
- Appendix architecture
- Vignette: splitting a technique-plus-tool paper
- Output format
What does the cav-supplementary skill do?
Use when deciding what belongs in a CAV (Computer Aided Verification) paper body versus its optional appendix and artifact, covering the LNCS page limits, the rule that reviewers are not obliged to read the appendix so decision-critical content stays in the body, where full proofs and benchmark tables live, and double-anonymous supplementary material for the anonymized categories.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-supplementary --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.