tacas-reproducibility
Use when strengthening TACAS (ETAPS) reproducibility, covering the clean evaluation-VM packaging that the artifact process assumes, pinned dependencies and offline execution, a claim-to-script mapping so every benchmark number regenerates, honest degrees of reproducibility, consistency between the paper and the artifact, and the category difference between a mandatory tool-paper artifact and a voluntary research-paper artifact.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-reproducibility --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 Reproducibility Use this before submission (for tool papers, before the mandatory artifact deadline) and again before camera-ready. At TACAS reproducibility is not a courtesy: for a **regular tool** or **tool-demonstration** paper the artifact is **mandatory and feeds acceptance**, and for a research or case-study paper a voluntary artifact earns the title-page badges. The goal is that an ETAPS evaluator, on a **clean virtual machine**, can rebuild your evidence and reach your numbers. ## Design for the clean ETAPS VM The artifact process assumes a provided VM image with bounded evaluator time. Package accordingly: ```text [Self-contained] ship a VM-ready package: a Dockerfile or a pinned environment (lockfile), with the tool prebuilt; not "apt-get install 30 things and hope" [Offline] no network access at run time; vendor every dependency, benchmark, and model [Bounded] a short smoke run that finishes in minutes, plus a documented full run with its expected (possibly long) runtime [Deterministic] fix seeds and tool options; state what is and is not deterministic [Documented] a README that orients an evaluator in one screen: what it is, how to run the smoke test, how to rep
- Design for the clean ETAPS VM
- Claim-to-script mapping (the heart of a TACAS artifact)
- Claim-to-evidence audit
- Degrees of reproducibility (state the one you achieved)
- Category difference
- Consistency and camera-ready pass
- Output format
What does the tacas-reproducibility skill do?
Use when strengthening TACAS (ETAPS) reproducibility, covering the clean evaluation-VM packaging that the artifact process assumes, pinned dependencies and offline execution, a claim-to-script mapping so every benchmark number regenerates, honest degrees of reproducibility, consistency between the paper and the artifact, and the category difference between a mandatory tool-paper artifact and a voluntary research-paper artifact.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-reproducibility --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 984 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.