Individual skill
sigcomm-experiments
Use when designing or auditing ACM SIGCOMM experiments — climbing the evidence ladder from microbenchmarks to testbed and trace replay to deployment, choosing baselines that match the deployed state of the art, reporting tail percentiles and variance over repeated trials, mapping break points, and holding the fair variable fixed.
SIGCOMM-Skills/skills/sigcomm-experiments/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,411
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- devops Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,957 bytes
Read excerpt
# SIGCOMM Experiments
Use this before submission when the evaluation is not yet locked. At SIGCOMM the experiments are
where a mechanism is believed or disbelieved, and the reviewer culture reads a setup for
realism, fairness, and honesty about where the mechanism breaks.
## Experiment audit
- Map each performance claim to a specific microbenchmark, testbed run, trace replay,
deployment measurement, or documented break point.
- Choose **baselines that fight back**: the strongest deployed alternative, tuned fairly, not a
straw man the mechanism was built to beat.
- **Report the distribution.** Give the relevant percentiles (P50, P99, and the tail that
hurts) with variance over repeated trials, and hold the fair variable — throughput, offered