atc-submission
Use when auditing an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission for HotCRP readiness — the paired two-page extended abstract plus full paper, the two-column 12/6-page budget, the double-blind anonymity sweep, ACM Open Access publication, and desk-reject triage before the early-June AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-submission --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.
# ATC Submission Run this audit before uploading to the ATC HotCRP site (`atc26.hotcrp.com`). ATC 2026 is the first **ACM SIGOPS Annual Technical Conference** — the continuation of the former **USENIX ATC** — so the process changed in the handover: a new **two-round, extended-abstract** review, a **June deadline**, a **Hong Kong / November** conference, and **ACM Open Access** publication. Every number below was read from the ATC 2026 SIGOPS call and the USENIX ATC '25 pages on 2026-07-09 via search renderings (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## The paired upload (the thing authors miss) ATC's first review round judges a **two-page extended abstract**, uploaded **together with the full paper** in one HotCRP submission: - The extended abstract gives the motivation and contribution and is **for review only — it is not published**. - It must **stand on its own**: a round-one reviewer may read *only* the abstract, and a round-two reviewer may read *only* the paper. Neither may assume the other. - A copy of the introduction can serve as the abstract **only if it fits two pages and reads self-contained** — usuall
- The paired upload (the thing authors miss)
- Format and page budget
- Double-blind sweep
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any anonymized artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|gitlab|zenodo\.org/record|acknowledg|grant|our (prior|previous) (system|work)' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/|hostname' | head grep -rniE 'university|@[a-z0-9.]+\.edu|cluster [a-z0-9-]+|internal-|corp\.' artifact/ --include='*.md' --include='*.sh' | head
What does the atc-submission skill do?
Use when auditing an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) submission for HotCRP readiness — the paired two-page extended abstract plus full paper, the two-column 12/6-page budget, the double-blind anonymity sweep, ACM Open Access publication, and desk-reject triage before the early-June AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-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 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.