ndss-reproducibility
Use when making an NDSS paper's results reconstructible — snapshotting live-network observations, pinning testbeds and toolchains, scrubbing traces that carry identities, and writing honest availability statements when ethics or vendor embargoes limit release.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-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.
# NDSS Reproducibility Network-security results decay: targets patch, providers change behavior, botnets die, and the population you measured in August is not the population of next March. Reproducibility at NDSS therefore means two different promises, and conflating them is the classic mistake: 1. **Reconstruction** — anyone can re-derive your numbers from what you recorded. 2. **Re-execution** — anyone can re-run your pipeline against the world and get *their* numbers, understanding why they differ from yours. Promise (1) unconditionally. Promise (2) only where the world cooperates. ## Freezing the measured world | Volatile thing | What to freeze at experiment time | | --- | --- | | Scanned population | Input list + source + retrieval date; per-target response snapshots | | Target software | Exact versions, build hashes, config files; patch level on the test date | | Network path | Vantage descriptions, traceroute-level context where relevant, ASN of probes | | Testbed | Topology file, firmware images (or their hashes), kernel/NIC settings | | Toolchain | Container image or lockfile for every analysis script; seeds for anything sampled | | Third-party feeds | Copies (or hashes +
- Freezing the measured world
- Traces are radioactive
- The claims ledger
- Honest availability statements
- Cheap habits that pay at rebuttal time
- Output format
What does the ndss-reproducibility skill do?
Use when making an NDSS paper's results reconstructible — snapshotting live-network observations, pinning testbeds and toolchains, scrubbing traces that carry identities, and writing honest availability statements when ethics or vendor embargoes limit release.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-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.