atc-related-work
Use when writing or auditing the related-work and positioning of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — covering the systems literature lanes, positioning against OSDI/SOSP/NSDI/EuroSys/FAST, writing delta-first comparisons, and keeping self-citation double-blind.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-related-work --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 Related Work Position the paper in the systems literature, not against a strawman. ATC's broad scope means your reviewers span subareas, and a related-work section that a storage reviewer and a networking reviewer both find fair is a signal the paper is well situated. Because review is **double-blind**, positioning and self-citation must be handled carefully. ## Cover the lanes a systems reviewer expects For most ATC papers, at least these lanes should be visible: - **The direct predecessors** — the systems and techniques you build on or replace, with the specific mechanism you change. - **The alternative approaches** — other ways the community has attacked this problem, and why yours differs (not just "we are better," but *how* the design differs and what that buys). - **The adjacent subareas** — where an idea from storage, networking, virtualization, or scheduling informs your design; ATC reviewers respect cross-pollination when it is credited. - **The measurement/experience literature** — prior studies of the phenomenon you address, so your motivation rests on evidence, not assertion. ## Delta-first positioning Write each comparison **delta-first**: state what the prior sy
- Cover the lanes a systems reviewer expects
- Delta-first positioning
- Sibling-venue awareness
- Double-blind self-citation
- Common failure modes
- Output format
What does the atc-related-work skill do?
Use when writing or auditing the related-work and positioning of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — covering the systems literature lanes, positioning against OSDI/SOSP/NSDI/EuroSys/FAST, writing delta-first comparisons, and keeping self-citation double-blind.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-related-work --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.