Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/cav-author-response
Use when drafting a CAV (Computer Aided Verification) author response (rebuttal) for a paper that has passed the two-stage review's first filter, covering how to answer soundness/proof objections, benchmark-fairness challenges, and novelty-delta doubts with verifiable evidence while preserving double-anonymity for Regular and Application papers.
Passed 21 of 22 test cases with the skill, and 14 of 22 without it.
and 11 more in the full report
7 fixed14 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Draft a stage-2 rebuttal outline for a CAV Regular paper. R1 questions Lemma 1 correctness (§3.1). R2 claims baseline CVC5 was not run with portfolio mode. Provide the response using the exact required bracketed tags for turn, priority issue, decision dimension, claim ledger, and anonymity check.
| Checked | Without skill | With skill |
|---|---|---|
| Contains the exact tag [Turn] | Missed | Passed |
| Contains the exact tag [Decision dimension] | Missed | Passed |
| Contains the exact tag [Anonymity check] | Missed | Passed |
The instructions your model reads when the skill loads.
Use this after CAV stage-2 reviews are released. At CAV the rebuttal exists only for papers that passed the stage-1 filter — the two-stage process means a rejected paper never reaches this turn. So the rebuttal is a focused instrument: answer what the two additional reviewers, and the two from stage 1, need in order to advocate for the paper in the PC discussion. For Regular and Application papers, the response must respect double-anonymity — do not reveal authors, the tool's real name, or identity-revealing repositories.
Treat the response as a claim ledger: for each reviewer concern, either resolve it with concrete evidence or explain precisely why the concern does not apply.
[R1.1] "The soundness proof assumes X, which fails for unbounded inputs."
-> Response: X is not assumed; Lemma 2 holds for unbounded inputs (the bound is only on
the encoding width, §3.2). Pointer: §3.2, Lemma 2.
[R2.1] "The baseline solver was not the latest version / not tuned."
-> Response: baseline is vA.B (latest release at submission); we used its default portfolio
as recommended in its README; per-instance data in the artifact confirms parity of limits.
[R2.2] "Novelty over <prior technique> is unclear."
-> Response: prior technique shares lemmas only propositionally; ours admits theory lemmas
under a re-derivation check (the soundness contribution), see §3.3 and Table 2.
The rule that turns a stage-2 paper into an acceptance: **answer the axis the reviewer raised, with
test cases passed, vs 14 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.