atc-supplementary
Use when deciding what belongs in the ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) two-page extended abstract, the 12-page paper body, the optional appendix, and the artifact — splitting content by review round and decision-criticality so nothing that decides acceptance lives where a reviewer is not required to read.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-supplementary --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 Supplementary ATC gives you four places to put content, each read by a different reviewer under a different rule: the **two-page extended abstract** (round one, two reviewers), the **12-page body** (round two, 3-4 reviewers), the **appendix** (optional reading), and the **artifact** (opened during round two and evaluated post-acceptance). Placing content correctly is a strategic decision, not a formatting one, because reviewers are **not required** to read the appendix and a round-one reviewer may read **only** the abstract. ## The placement rule **Anything that decides acceptance goes in a place the deciding reviewer is required to read.** - Round-one acceptance is decided from the **extended abstract** → the problem, contribution, headline result, and honest cost must be *in the abstract*. - Round-two acceptance is decided from the **body** → every load-bearing design detail, baseline, and result must be *in the 12 pages*. - The **appendix** holds support a curious reviewer *may* consult — extra graphs, proofs, parameter tables — never a result the verdict depends on. - The **artifact** holds runnable evidence and full data — it strengthens trust and earns badges, but the p
- The placement rule
- What goes where
- The extended abstract is not a teaser
- The appendix is not overflow
- Consistency across the four places
- Decision procedure
- Output format
What does the atc-supplementary skill do?
Use when deciding what belongs in the ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) two-page extended abstract, the 12-page paper body, the optional appendix, and the artifact — splitting content by review round and decision-criticality so nothing that decides acceptance lives where a reviewer is not required to read.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-supplementary --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.