nsdi-reproducibility
Use when making an NSDI paper's results reconstructible — capturing testbed topology, trace provenance, and configuration while experiments run, planning which datasets can ship publicly, and keeping the paper and artifact from drifting apart so badge evaluation and the Community Award stay reachable.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-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.
# NSDI Reproducibility A networked-systems result is a function of topology, traffic, timing, and code — and three of those four are absent from the PDF unless deliberately recorded. NSDI rewards the discipline institutionally: artifact badges after acceptance and a **Community Award** for the best paper whose code and/or dataset is public by the final-papers deadline. But the work happens during the experiments, not after the decision email. ## The four provenance ledgers Keep each as a versioned file next to the results it explains: | Ledger | Contents | Loss mode it prevents | |---|---|---| | Topology | node specs, NIC/switch models, link speeds, RTT matrix, kernel + NIC settings | "worked on our cluster," unreproducible knee points | | Traffic | trace source + collection context, scaling/anonymization transforms, synthetic-generator parameters + seeds | headline numbers tied to data nobody can regenerate | | Configuration | every config diff from defaults, per system **and per baseline** | untuned-baseline accusations you cannot rebut | | Run | per-experiment: commit hash, config snapshot, fault schedule, raw-log location, analysis-script hash | figures that cannot be regenerat
- The four provenance ledgers
- Determinism is different here
- What can actually ship?
- Wiring it into the repo
- Blind now, open later
- Cheap wins ordered by payoff
- Signs the discipline is slipping
- Output format
Layout that keeps paper and artifact from drifting experiments/ figures/ Makefile # every paper figure regenerated from raw logs: paper/ claims.md # claim -> exp-id -> figure mapping, reviewed at freeze
What does the nsdi-reproducibility skill do?
Use when making an NSDI paper's results reconstructible — capturing testbed topology, trace provenance, and configuration while experiments run, planning which datasets can ship publicly, and keeping the paper and artifact from drifting apart so badge evaluation and the Community Award stay reachable.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-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 984 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.