atc-workflow
Use when planning an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) campaign end to end — running the year backward from the early-June deadline through the two review rounds, the rebuttal, conditional-acceptance shepherding, the post-acceptance artifact evaluation, and the ACM Open Access camera-ready for the November Hong Kong conference.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-workflow --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 Workflow Plan the campaign backward from the deadline. ATC 2026 — the first **ACM SIGOPS** edition of the former **USENIX ATC** — runs on a calendar and a review structure that both changed in the transition: an **early-June 2026** submission deadline (AoE; 1 vs. 10 June unresolved across renderings — 待核实), a **two-round, extended-abstract** review, **conditional acceptance with shepherding**, a separate **artifact-evaluation** track, and the conference in **Hong Kong, 15-18 November 2026**. Reopen the SIGOPS call for the exact dates before committing to any of the offsets below. ## The arc (backward from the deadline) ```text [T-0 Submission] paired upload: 2-page extended abstract + full paper on atc26.hotcrp.com [Round one] two reviewers judge each extended abstract; below-bar papers cut early [Round two] 3-4 reviewers read the full paper of survivors [Rebuttal] ~1 page: correct factual misreadings; note prior-submission changes if any [Decision] conditional accept / reject [Shepherding] a PC shepherd signs off required revisions before final acceptance [Artifact evaluation] separate post-acceptance AEC track -> Available / Functional / Reproduced [Camera-ready] de-anonymi
- The arc (backward from the deadline)
- Backward plan from the June deadline
- Between submission and decision
- After a conditional accept
- Calendar reconnaissance
- Reverify each cycle
- Output format
What does the atc-workflow skill do?
Use when planning an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) campaign end to end — running the year backward from the early-June deadline through the two review rounds, the rebuttal, conditional-acceptance shepherding, the post-acceptance artifact evaluation, and the ACM Open Access camera-ready for the November Hong Kong conference.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-workflow --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.