Individual skill
sigcomm-reproducibility
Use when strengthening the reproducibility evidence of an ACM SIGCOMM paper — topology and testbed ledgers, traffic workload and trace provenance, configuration and version pinning, tail-percentile run counts and variance, legal data-release decisions, and consistency between the paper's claims and the artifact that backs them.
SIGCOMM-Skills/skills/sigcomm-reproducibility/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- 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,403
- 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
- legal Derived category
- data Derived category
- research 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 · 4,250 bytes
Read excerpt
# SIGCOMM Reproducibility
Use this before submission and again before the artifact deadline. SIGCOMM's culture treats a
result as a claim a stranger should be able to rebuild; reproducibility here is largely about
whether the **network conditions** behind a number are recorded well enough to recreate.
Reopen the current Call for Artifacts to confirm the process for this edition.
## Evidence map
- Map each reported number to a rebuildable location: a script, a logged run, a config, and
the figure it feeds.
- For every measurement, record the **topology** (physical or emulated), the **traffic**
(workload generator or trace, with provenance), the **configuration** (every parameter),
and the **environment** (kernel, NIC, switch firmware, data-plane toolchain).