Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/cav-topic-selection
Use when deciding whether a formal-methods project belongs at CAV (Computer Aided Verification) or should be routed to TACAS, FMCAD, VMCAI, LPAR/IJCAR, POPL/PLDI/OOPSLA, or a journal (FMSD/JAR/TOCL), and when choosing the right CAV category — Regular, Short Tool, Short Application, or Industrial Experience & Case Study.
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
and 5 more in the full report
6 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the precise maximum page limit for a Regular Paper submission at CAV?
| Checked | Without skill | With skill |
|---|---|---|
| States the Regular Paper page limit is 18 pages | Missed | Passed |
The instructions your model reads when the skill loads.
Decide the venue and the category before drafting. CAV — the International Conference on Computer Aided Verification — is the flagship venue for computer-aided formal analysis of hardware and software systems: model checking, SMT and theorem proving, program analysis and synthesis, and their tools. Its papers are Springer LNCS chapters read by verification researchers, so reviewers reward a durable verification contribution with a stated guarantee, not a systems demo or an ML result with a verification label attached.
At CAV you choose both a venue (CAV vs. its siblings) and a category (Regular vs. Tool vs. Application vs. Industrial). Get the venue right first, then the category — a strong tool filed as a Regular Paper, or a technique squeezed into a 10-page tool paper, wastes the fit.
| Signal in your project | Better home | Why |
|---|---|---|
| A general verification technique/algorithm with a soundness/completeness result, mature enough for the flagship | CAV | Flagship scope; the Regular-Paper archetype |
| Emphasis on tools, algorithms, and their construction/analysis, or you want the ETAPS calendar | TACAS | Tools and Algorithms for the Construction and Analysis of Systems; overlaps heavily but is a distinct venue |
| Hardware-oriented or applied model checking, or a formal-methods-in-design focus | FMCAD | Formal Methods in Computer-Aided Design |
| Verification, model checking, and abstract interpretation with a foundations flavor, often earlier-stage | VMCAI | Verification, Model Checking, and Abstract Interpretation |
| Automated/interactive theorem proving or logic-focused | IJCAR / LPAR / ITP / CADE | Reasoning and proof communities |
| The core is a programming-language semantics, type system, or PL analysis | POPL / PLDI / OOPSLA | PL venues; verification is a means, not the contribution |
| The study is too long or too deep for the page limit | FMSD / JAR / TOCL / STTT | Journals with no conference page ceiling |
CAV and TACAS overlap the most; the honest tie-breakers are the calendar (CAV is annual in mid-year, often under FLoC or standalone; TACAS runs at ETAPS in spring) and community pull for your subarea. A strong paper is publishable at either — route to the nearer honest fit.
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.