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.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-author-response --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 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 affect
What does the tacas-author-response skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-author-response --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.