tacas-artifact-evaluation
Use when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers), what the AEC checks on the clean evaluation VM, DOI-issuing archives, and evaluator-proof documentation.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-artifact-evaluation --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 Artifact Evaluation Use this for the artifact track. TACAS treats the artifact as a **first-class citizen**, and the process differs from most venues in two ways: for **tool** papers it is **mandatory and runs in parallel with paper review**, and badging follows the **ETAPS Artifact Badge** guidelines, decided by the **Artifact Evaluation Committee (AEC)** and printed on the paper's title page. ## The two rounds (know which one you are in) | Round | Applies to | Timing | Consequence | |---|---|---|---| | Round 1 — mandatory | Regular **tool** + **tool-demonstration** papers | Submitted right after the paper, evaluated **with the PC** | Outcome **feeds the acceptance decision** | | Round 2 — voluntary | Regular **research** + **case-study** papers | **After** acceptance notification | Earns title-page badges; does not gate acceptance | The consequence for a tool paper is blunt: a package that does not build or run on the clean evaluation VM can cost the paper, not merely a badge. Treat the artifact as a co-equal deliverable due about two weeks after the paper. ## The ETAPS Artifact Badges | Badge | What it certifies | What earns it | |---|---|---| | **Available** | The artif
- The two rounds (know which one you are in)
- The ETAPS Artifact Badges
- What the AEC opens first
- Packaging plan
- Anonymity by category (do not get this backwards)
- Worked vignette: badging a model-checking tool
- Calibration
- Output format
What does the tacas-artifact-evaluation skill do?
Use when packaging a TACAS (ETAPS) artifact for the ETAPS Artifact Badges (Available, Functional, Reusable), covering the two-round model (mandatory, PC-parallel evaluation for tool and tool-demo papers vs voluntary post-acceptance evaluation for research and case-study papers), what the AEC checks on the clean evaluation VM, DOI-issuing archives, and evaluator-proof documentation.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-artifact-evaluation --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.