atc-writing-style
Use when drafting or revising an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — writing a self-standing two-page extended abstract for the round-one gate, structuring the implementation-and-measurement narrative, reporting costs beside gains, and holding the two-column 12-page budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-writing-style --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 Writing Style Write for two audiences in two rounds. In round one, two reviewers read only your **two-page extended abstract**; in round two, 3-4 reviewers read the full paper. The abstract is **review-only, not published, and must stand alone**. So ATC writing has a demand no single-round venue makes: the paper's core argument must fit, self-contained, into two pages *and* expand faithfully into twelve. ## The self-standing extended abstract (round-one surface) A round-one reviewer who reads only the abstract should finish knowing: 1. **The systems problem** — a pain a builder or operator recognizes, in the first breath. 2. **Why the current design is inadequate** — the specific limitation your work removes. 3. **The contribution** — the system or technique, stated as what it *does*, not "novel." 4. **The evidence** — the real testbed and the headline result (with the metric that matters, e.g., tail latency, throughput at matched cost). 5. **The honest cost** — what the design trades away, named not hidden. Test it: hand the two pages to a systems colleague *without* the paper and ask them to state the problem, contribution, testbed, and result. If they cannot, the abstract
- The self-standing extended abstract (round-one surface)
- The full-paper arc
- Report costs beside gains (the ATC trust move)
- Page-budget discipline (two columns, 12 pages)
- Systems-prose specifics
- Anti-patterns (ATC-specific)
- Output format
What does the atc-writing-style skill do?
Use when drafting or revising an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — writing a self-standing two-page extended abstract for the round-one gate, structuring the implementation-and-measurement narrative, reporting costs beside gains, and holding the two-column 12-page budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-writing-style --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.