NSDI Skills
A 12-skill depth pack for NSDI submissions: networked-systems venue fit, the twice-a-year deadline calendar, HotCRP submission audits, one-shot revise-and-resubmit handling, deployment-grade evaluation, artifact badges and the Community Award, and USENIX open-access final papers. Grounded in the NSDI '27 and NSDI '26 official pages checked on 2026-07-08.
Skills in this plugin
11- ▌ Nsdi Submission · brycewang-stanfordUse when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap with references and appendices outside it, track-dependent anonymization, the eight-paper author cap, and the resubmission-ban check.
- ▌ Nsdi Experiments · brycewang-stanfordUse when designing or auditing the evaluation of an NSDI submission — choosing traces, testbeds, and deployment evidence, sizing scale and failure-injection experiments, picking baselines that fight back, and reporting tail behavior so networked-systems reviewers can see where the design wins, loses, and breaks.
- ▌ Nsdi Camera Ready · brycewang-stanfordUse when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's open-access proceedings for the May symposium.
- ▌ Nsdi Related Work · brycewang-stanfordUse when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and handling self-citations and concurrent submissions under double-blind rules.
- ▌ Nsdi Supplementary · brycewang-stanfordUse when splitting NSDI material across the 12-page body, the appendix pages the CFP allows beyond references, HotCRP auxiliary-material uploads for critical online content, and the one-shot-revision packet — deciding what reviewers must see in-body versus what merely supports it.
- ▌ Nsdi Writing Style · brycewang-stanfordUse when drafting or revising NSDI prose — building the operational-pain-to-design-principle arc, fitting argument and figures into 12 pages with references and appendices outside the cap, calibrating claims to trace and testbed evidence, and writing for reviewers who read tail percentiles before adjectives.
- ▌ Nsdi Review Process · brycewang-stanfordUse when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline resubmission ban, reviewer continuity across revisions, and what each decision letter actually commits the authors to.
- ▌ Nsdi Author Response · brycewang-stanfordUse when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the submission when no response phase exists.
- ▌ Nsdi Reproducibility · brycewang-stanfordUse 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.
- ▌ Nsdi Topic Selection · brycewang-stanfordUse when judging whether a project belongs at NSDI, picking among its research, operational-systems, and frontiers tracks, or re-routing to SIGCOMM, OSDI, SOSP, FAST, or SIGMETRICS — testing the networking-stack contribution, the CFP's out-of-scope lines, and which of the two yearly deadlines to aim at.
- ▌ Nsdi Artifact Evaluation · brycewang-stanfordUse when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for the Community Award.