tacas-related-work
Use when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast against the nearest tools and algorithms, crediting the benchmarks and solvers you build on, keeping self-citations anonymous for double-blind research papers, and handling competition-tool and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-related-work --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.
# TACAS Related Work Use this to audit novelty and eligibility. TACAS reviewers are close to the verification literature and to the tools it produces, so they expect to see where your algorithm or tool sits relative to the nearest prior work — as a **delta**, not a catalog. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising authors. ## Positioning checks - **Separate the algorithmic novelty from the engineering.** What is new: a new decision procedure, a new encoding, a new abstraction, a tool that first makes a technique usable, or a case study that first applies it at scale? Name it precisely. - **Cover the verification venues.** TACAS reviewers expect the flagships and the journals, not just the papers nearest your method (see the table). Missing the obvious CAV/VMCAI/FMCAD predecessor reads as unaware. - **Credit what you build on.** If you use an SMT solver, a benchmark suite, or a model-checking backend, cite it — TACAS is a tool-and-algorithm community and reviewers notice uncredited infrastructure or benchmarks. - **Write delta-first.** Each closely related tool/algorithm gets one sentence on what it did and one on what you d
- Positioning checks
- Verification literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the tacas-related-work skill do?
Use when positioning a TACAS (ETAPS) submission against the verification literature across TACAS, CAV, VMCAI, FMCAD, SPIN, and journals (STTT, FMSD), writing delta-first contrast against the nearest tools and algorithms, crediting the benchmarks and solvers you build on, keeping self-citations anonymous for double-blind research papers, and handling competition-tool and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-related-work --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.