atc-reproducibility
Use when building the reproducibility story for an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — pinning testbed and software environments, providing a turnkey path from the artifact to the headline numbers, and preparing an anonymized-but-runnable review package ahead of the Available/Functional/Reproduced badges.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-reproducibility --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 Reproducibility Build the reproducibility story alongside the system, not at the deadline. ATC has an active artifact culture inherited from USENIX: reviewers expect a runnable, anonymized artifact at review time, and after acceptance an Artifact Evaluation Committee awards **Available / Functional / Reproduced** badges (see `atc-artifact-evaluation`). The through-line is that a systems result other people can re-run is worth more than one they must take on faith — and systems provenance cannot be reconstructed after the fact. ## Pin what you cannot reconstruct Record these **at collection time**; none can be recovered at the deadline: ```text [Hardware] CPU/NIC/SSD models, core/memory counts, firmware/BIOS where it matters [OS/kernel] kernel version, distro, relevant sysctl/tuning, hugepages/NUMA settings [Toolchain] compiler, library, and runtime versions; build flags [Workload] trace source + extraction date, generator version + seeds, request mix [Method] warm-up window, measurement duration, run count, aggregation method [Code] commit SHAs for your system and every baseline; patches applied ``` ## A turnkey path to the headline numbers The single most valuable artifact p
- Pin what you cannot reconstruct
- A turnkey path to the headline numbers
- Pinned, portable environments
- Anonymized-but-runnable review package
- Honest reproducibility posture
- Output format
What does the atc-reproducibility skill do?
Use when building the reproducibility story for an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — pinning testbed and software environments, providing a turnkey path from the artifact to the headline numbers, and preparing an anonymized-but-runnable review package ahead of the Available/Functional/Reproduced badges.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-reproducibility --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.