tacas-writing-style
Use when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence, category-appropriate structure (research vs tool vs case-study vs tool-demo), disciplined use of the 16-page (or 6-page) LNCS budget, and correct handling of double-blind wording for research papers.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-writing-style --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 Writing Style Use this when revising the main paper. TACAS papers are LNCS articles read by verification experts, so they need the **contribution stated precisely on the first page** and **claims a reviewer can check** — a soundness argument for a research paper, a working tool with reproducible numbers for a tool paper. The failure this skill prevents is a paper that gestures at "efficiency" and "novelty" without a crisp algorithmic claim or an honest evaluation. ## Revision rules (all categories) - **Lead with the construction/analysis problem and the contribution.** State what the paper builds or decides, on what inputs, and how — before any adjective. A verification reader wants the object of study (a property, a system model, a decision problem) named immediately. - **State the soundness claim explicitly.** "Sound," "sound and complete," "complete up to bound *k*," or "unsound but effective, and here is why that is acceptable" — say which, and point to the argument. An unstated correctness posture is the first thing a TACAS reviewer probes. - **Pair every empirical claim with honest evidence** — named benchmarks, a fair baseline, wall-clock time on stated hardware, and
- Revision rules (all categories)
- Category skeletons
- Sentence-level rewrites
- Soundness-and-evidence discipline
- Vignette: compressing a research paper to 16 pages
- Output format
What does the tacas-writing-style skill do?
Use when revising a TACAS (ETAPS) paper for a clear construction-or-analysis contribution on the first page, a stated soundness/completeness claim, honest benchmark evidence, category-appropriate structure (research vs tool vs case-study vs tool-demo), disciplined use of the 16-page (or 6-page) LNCS budget, and correct handling of double-blind wording for research papers.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-writing-style --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.