Individual skill

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.

ATC-Skills/skills/atc-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,393
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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."
Back to top