Agent skill

tacas-submission

Use when auditing a TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool, tool-demonstration), the correct LNCS page limit and llncs.cls format, the per-category blind mode (double-blind research vs single-blind tool/case-study), the mandatory tool-paper artifact deadline, and desk-reject triage before the firm ETAPS deadline.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-submission --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: TACAS-Skills/skills/tacas-submission/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 984 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# TACAS Submission Run this audit before uploading to the TACAS **EasyChair** site. TACAS is a main conference of **ETAPS**, publishing in **Springer LNCS** (gold open access), and — unlike a single-track venue — it has **four paper categories** whose rules differ in page limit, anonymity, and artifact obligation. Every number below was read from the TACAS 2026 / ETAPS 2026 joint call on 2026-07-09 via search renderings of the `etaps.org` pages (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ETAPS deadlines are advertised as **firm and not extended**. ## Step 0 — pick the category (it sets every other rule) | Category | Page limit (llncs.cls) | Blind mode | Artifact | |---|---|---|---| | Regular research paper | ≤16 pages | **Double-blind** | Voluntary, post-acceptance | | Case-study paper | ≤16 pages | Single-blind | Voluntary, post-acceptance | | Regular tool paper | ≤16 pages | Single-blind | **Mandatory**, submitted after the paper, gates acceptance | | Tool-demonstration paper | ≤6 pages | Single-blind | **Mandatory**, submitted after the paper, gates acceptance | Page limits **exclude the bibliography and a clearly

What's inside
Steps it walks through
  1. Step 0 — pick the category (it sets every other rule)
  2. Format and page budget
  3. The blind sweep — but only where it applies
  4. The mandatory-artifact reality (tool and tool-demo papers)
  5. Desk-risk triage
  6. Final-week order of operations
  7. Reverify each cycle
  8. Output format
Commands it runs
Research-paper (double-blind) anonymity check on the final PDF and any review artifact
pdfinfo paper.pdf | grep -Ei 'author|creator|producer'
pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|acknowledg|grant|thanks' | head
grep -rniE 'our (tool|group|lab)|university of|@[a-z0-9.]+\.edu' artifact/ --include='*.md' | head
More from Awesome-Journal-Skills
All skills →
About this skill
What does the tacas-submission skill do?

Use when auditing a TACAS (ETAPS) submission for EasyChair readiness, covering the choice among the four paper categories (research, case-study, regular tool, tool-demonstration), the correct LNCS page limit and llncs.cls format, the per-category blind mode (double-blind research vs single-blind tool/case-study), the mandatory tool-paper artifact deadline, and desk-reject triage before the firm ETAPS deadline.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill tacas-submission --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 984 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.

Keep going