tacas-review-process
Use when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single annual PC round with a rebuttal, the parallel mandatory artifact evaluation that feeds tool-paper acceptance, accept/reject decisions, and how TACAS's process differs from CAV's and from a journal's.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-review-process --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 Review Process Model the pipeline before interpreting any single review. TACAS's process has three features that surprise authors arriving from other venues: reviewing is **blind by category**, the decision for a **tool paper** depends on a **parallel artifact evaluation**, and the whole thing runs in a **single annual round** on the ETAPS schedule with a short rebuttal — not a rolling or multi-round journal cycle. ## Process model - Submission and review run on **EasyChair** under the ETAPS joint schedule. Reviewing is **per-category**: **regular research papers are double-blind**; **case-study, regular tool, and tool-demonstration papers are single-blind**. - Each paper is read by multiple PC members who weigh, for a research paper, the **soundness and significance of the algorithm**; for a tool paper, the **tool's contribution and its working artifact**; for a case study, the **realism of the system and the honesty of the lessons**. - For **regular tool and tool-demonstration** papers, a **mandatory artifact** is evaluated by the Artifact Evaluation Committee **in parallel with the PC**, and the artifact outcome **feeds the acceptance decision** — a paper whose artifact
- Process model
- Reading a decision against the category
- How TACAS differs from its siblings
- Who reads you
- Where author leverage actually exists
- Misreadings to avoid
- Output format
What does the tacas-review-process skill do?
Use when reasoning about how a TACAS (ETAPS) submission is evaluated, covering the per-category blind model (double-blind research vs single-blind tool/case-study), the single annual PC round with a rebuttal, the parallel mandatory artifact evaluation that feeds tool-paper acceptance, accept/reject decisions, and how TACAS's process differs from CAV's and from a journal's.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-review-process --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.