Individual skill
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.
TACAS-Skills/skills/tacas-related-work/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- 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,409
- 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
- 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,381 bytes
Read excerpt
# 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