SkillAgentSearch skills...

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 wh…

Install / Use

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-supplementary

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Our assessment of atc-supplementary

atc-supplementary scores 87/100 on our quality scale, 2125th of 4,607 Development & Engineering skills we index (top 47%).

Its SKILL.md is 4.4 KB long, well organised into 8 sections with 2 code examples: a solid amount of guidance for an agent.

With 1,158 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 21 days ago, so atc-supplementary is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

atc-supplementary compared with similar skills

All 4 of these similar skills score higher than atc-supplementary; compare them before choosing.

SkillScoreStarsUpdatedFormat
atc-supplementary (this skill)by brycewang-stanford871.2k21d agoSKILL.md
ai-job-searchby MadsLorentzen10045.1ktodayCLAUDE.md
claude-howtoby luongnv8910041.8k6d agoCLAUDE.md
algorithmic-artby anthropics100177.9k13d agoSKILL.md
pptxby anthropics100177.9k13d agoSKILL.md

Frequently asked questions

How do I install atc-supplementary?
Run npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-supplementary. The install tabs above show the steps for each supported agent.
Which AI agents does atc-supplementary work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is atc-supplementary safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is atc-supplementary still maintained?
The repository was last updated 21 days ago, so atc-supplementary is actively maintained.

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>

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryDevelopment
Updated21d ago
Forks153

Languages

Stata

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions