Individual skill

tacas-author-response

Use when drafting a TACAS (ETAPS) author response for the rebuttal window, covering the short single-round rebuttal, answering soundness and benchmark-fairness objections with checkable evidence, addressing artifact concerns for tool papers, respecting the per-category blind model when it applies, and reading which objections a rebuttal can and cannot move.

TACAS-Skills/skills/tacas-author-response/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# TACAS Author Response

Use this after TACAS reviews are released in the **rebuttal window**. TACAS has **one speaking
turn**: a short, targeted author response before the PC finalizes decisions — not a journal-style
revise-and-resubmit. The job is to correct misreadings and supply the one or two checkable facts
that move a borderline paper, not to rewrite the paper.

## Triage

- Answer what affects the decision: **soundness** of the algorithm, **fairness and reproducibility**
  of the evaluation, **artifact** function (for tool papers), correctness of a proof step, and
  genuine misreadings.
- Use evidence that already exists in the submitted paper or artifact, or a number you can state
  now — never a vague promise of future work.
Back to top