/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
$ npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-supplementary --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/atc-supplementary
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
atc-supplementary.SKILL.mdname: atc-supplementary
description: 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.
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 paper must be judgeable without executing it.
What goes where
| Content | Home | Why | |---|---|---| | Problem, contribution, testbed, headline result, key cost | **Extended abstract** | The round-one decision surface; must stand alone | | Design rationale, implementation, main experiments, fair baselines, tails/variance | **Body (≤12 pp)** | The round-two decision surface; nothing acceptance-critical may leave it | | Extra sensitivity graphs, parameter sweeps, proofs, extended tables | **Appendix** | Optional depth; reviewers not required to read it | | Full code, traces/datasets, configs, claim-to-experiment scripts | **Artifact** | Runnable evidence + badge material; paper still judged without running it |
The extended abstract is not a teaser
The most common ATC mistake is treating the extended abstract as a marketing blurb that depends on the paper. It is a **self-contained argument** that must survive being read *instead of* the paper (see `atc-writing-style`). Move the real problem, the real contribution, and a real result into it; do not defer them to "as shown in the paper."
The appendix is not overflow
The second common mistake is using the appendix to dodge the 12-page limit by exiling results a reviewer must weigh. If a graph is needed to believe a claim, it belongs in the body; if it is merely reassuring, it belongs in the appendix. Ask: **would a reviewer who skips this change their score?** If yes, it is body content.
Consistency across the four places
- The number in the abstract, the body, the appendix, and the artifact output must **match**.
Divergent numbers across places are a credibility hit and a frequent reviewer catch.
- The claim-to-experiment map (see `atc-experiments`, `atc-reproducibility`) should let a reviewer
trace each body claim to an artifact script and each artifact output back to a body figure.
- Keep all four **double-blind**: an appendix or artifact often leaks identity (hostnames, owner
strings, system names) even when the body is clean.
Decision procedure
[For each result] which round decides it? -> place it where that round's reviewer must read
[Abstract test] can a reviewer accept/reject from the 2 pages alone? if not, move content in
[Body test] is any acceptance-critical claim only in an appendix/artifact? if yes, move it in
[Appendix test] would skipping this change a score? if yes, it is body content, not appendix
[Consistency] do the numbers match across abstract/body/appendix/artifact? anonymity intact?
Output format
[Extended abstract] self-standing, decision-complete for round one? yes/no
[Body] all acceptance-critical content inside 12 pages? leaks to appendix/artifact?
[Appendix] optional-only? nothing score-changing exiled here?
[Artifact] runnable evidence + full data; paper judgeable without it? anonymized?
[Move queue] <content to relocate, with target location and reason>
Read more
name: atc-supplementary description: 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.
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 paper must be judgeable without executing it.
What goes where
| Content | Home | Why | |---|---|---| | Problem, contribution, testbed, headline result, key cost | **Extended abstract** | The round-one decision surface; must stand alone | | Design rationale, implementation, main experiments, fair baselines, tails/variance | **Body (≤12 pp)** | The round-two decision surface; nothing acceptance-critical may leave it | | Extra sensitivity graphs, parameter sweeps, proofs, extended tables | **Appendix** | Optional depth; reviewers not required to read it | | Full code, traces/datasets, configs, claim-to-experiment scripts | **Artifact** | Runnable evidence + badge material; paper still judged without running it |
The extended abstract is not a teaser
The most common ATC mistake is treating the extended abstract as a marketing blurb that depends on the paper. It is a **self-contained argument** that must survive being read *instead of* the paper (see `atc-writing-style`). Move the real problem, the real contribution, and a real result into it; do not defer them to "as shown in the paper."
The appendix is not overflow
The second common mistake is using the appendix to dodge the 12-page limit by exiling results a reviewer must weigh. If a graph is needed to believe a claim, it belongs in the body; if it is merely reassuring, it belongs in the appendix. Ask: **would a reviewer who skips this change their score?** If yes, it is body content.
Consistency across the four places
- The number in the abstract, the body, the appendix, and the artifact output must **match**.
Divergent numbers across places are a credibility hit and a frequent reviewer catch.
- The claim-to-experiment map (see `atc-experiments`, `atc-reproducibility`) should let a reviewer
trace each body claim to an artifact script and each artifact output back to a body figure.
- Keep all four **double-blind**: an appendix or artifact often leaks identity (hostnames, owner
strings, system names) even when the body is clean.
Decision procedure
[For each result] which round decides it? -> place it where that round's reviewer must read [Abstract test] can a reviewer accept/reject from the 2 pages alone? if not, move content in [Body test] is any acceptance-critical claim only in an appendix/artifact? if yes, move it in [Appendix test] would skipping this change a score? if yes, it is body content, not appendix [Consistency] do the numbers match across abstract/body/appendix/artifact? anonymity intact?
Output format
[Extended abstract] self-standing, decision-complete for round one? yes/no [Body] all acceptance-critical content inside 12 pages? leaks to appendix/artifact? [Appendix] optional-only? nothing score-changing exiled here? [Artifact] runnable evidence + full data; paper judgeable without it? anonymized? [Move queue] <content to relocate, with target location and reason>
Stanford REAP × CoPaper.AI · 由斯坦福实证方法论团队精选与维护 访问 copaper.ai 微信:CoPaper.AI 按 11 个主流学科板块覆盖 经管与商科 社会科学 人文学科 数学与物理科学 生命科学 医学与健康 工程与技术 计算机科学与 AI 体育科学 点击任一学科名可跳转到对应说明;每类下的代表子领域在正文总览中完整列出。下方封面墙按 venue 导航,完整分类见覆盖一览。 🧭 布局指南 · 📚 Skill Pack 一览 · ⚡ 如何使用 · 🧪 自动实证
Other skills on awesome-journal-skills.
- /aaai-artifact-evaluation
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
Open skill - /aaai-author-response
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round
Open skill - /aaai-camera-ready
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and
Open skill - /aaai-experiments
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and
Open skill - /aaai-related-work
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a
Open skill - /aaai-reproducibility
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that
Open skill

