atc-topic-selection
Use when deciding whether a computer-systems project belongs at ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) or should be routed to OSDI, SOSP, NSDI, EuroSys, FAST, or a workshop like HotOS/HotStorage — distinguishing ATC by its broad practical scope, its Deployed Systems / experience lane, the breadth-vs-selectivity trade, and the November/June calendar.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-topic-selection --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 Topic Selection Decide the venue before drafting. ATC — the ACM SIGOPS Annual Technical Conference, for about fifty years the **USENIX Annual Technical Conference** — is the systems community's **broad, practical** venue. It emphasizes **implementations and experimental results** across the whole systems stack and takes a wider slice than the more selective OSDI/SOSP flagships. The decisive question is rarely "is this systems?" but **"is this a solid, useful, measured systems result — and is ATC's breadth the right home versus a more specialized or more selective venue?"** ## What ATC rewards - **Built and measured systems** across a broad scope: operating systems, runtime systems, parallel and distributed systems, storage, networking, security and privacy, virtualization, hardware-software interaction, performance and workload characterization, reliability, availability, scalability, energy, and bug-finding / tracing / troubleshooting — "of all scales, from embedded devices to data centers and clouds." - **Useful over merely novel.** A solid, well-engineered, carefully measured system that a flagship might call incremental is squarely in scope if it is real and the evaluatio
- What ATC rewards
- Sibling-venue routing table
- The breadth and deployed-systems tests
- Evidence maturity, without the ladder cliché
- Cheap reconnaissance before committing
- Decision procedure
What does the atc-topic-selection skill do?
Use when deciding whether a computer-systems project belongs at ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) or should be routed to OSDI, SOSP, NSDI, EuroSys, FAST, or a workshop like HotOS/HotStorage — distinguishing ATC by its broad practical scope, its Deployed Systems / experience lane, the breadth-vs-selectivity trade, and the November/June calendar.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-topic-selection --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.