atc-experiments
Use when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-experiments --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 Experiments Match the evidence to the claim. ATC is the systems community's **implementation-and-measurement** venue: reviewers read for measured behavior on a real system, not asymptotics or accuracy on a dataset. In round two, 3-4 reviewers close to your subarea will open the artifact and probe whether the numbers are end-to-end, fair, and honest about cost. Design the evaluation so their first three objections are already answered. ## Match evidence to claim shape | If your claim is... | The evidence ATC expects | |---|---| | "Faster / lower latency" | End-to-end latency **including tails (p99/p999)** and throughput at a **matched** operating point, on a described testbed | | "Lower overhead / cheaper" | The resource cost (CPU, memory, writes, energy) measured, at matched function — not just the headline win | | "Scales" | Measurements across a real range of load/nodes/cores with the scaling curve and where it bends | | "More reliable / correct" | Fault-injection or crash/recovery experiments, not just steady-state runs | | "Useful in practice" (experience) | Production-derived workloads and lessons; what broke and what generalizes | ## Real testbeds and workloads - **Desc
- Match evidence to claim shape
- Real testbeds and workloads
- Fair baselines
- End-to-end plus microbenchmarks
- Tails, variance, and honest reporting
- Provenance you cannot reconstruct later
- Special cases
- Output format
What does the atc-experiments skill do?
Use when designing or auditing the evaluation of an ATC (ACM SIGOPS Annual Technical Conference, formerly USENIX ATC) systems paper — matching evidence to the claim with real testbeds, fair baselines, end-to-end plus microbenchmark results, tail-latency and variance reporting, workload realism, and honest cost accounting.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill atc-experiments --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.