nsdi-related-work
Use 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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-related-work --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 Related Work Related work at NSDI answers one reviewer question: *what does this design let us do that the systems we already have do not?* Coverage gaps read as either ignorance or evasion, and the venue's open-access record removes every excuse for both. ## The lanes an NSDI reviewer expects swept | Lane | Where it lives | What must be said about it | |---|---|---| | Direct competitors | NSDI, SIGCOMM, OSDI, SOSP | Mechanism-level delta, ideally measured head-to-head | | Same problem, other stack layer | SIGCOMM (protocol), OSDI/SOSP (host), FAST (storage) | Why this layer is the right place to solve it | | Same technique, other domain | broad systems + ML-systems venues | What the networked setting breaks or changes | | Measurement/characterization basis | IMC, NSDI measurement papers | Which observed phenomena motivated the design | | Deployed/industrial precedent | operational-track papers, provider tech reports | What production experience the design inherits or contradicts | | Early/idea-stage neighbors | HotNets, frontiers-track papers | That the idea's grown-up form differs from the sketch | Both **cohorts of the current edition** count as literature: NSDI posts spr
- The lanes an NSDI reviewer expects swept
- Verification: the venue must be proven
- Positioning moves that work at this venue
- Double-blind mechanics for citations
- Sequencing the sweep across the two-deadline year
- Failure patterns
- Where the section lives
- Output format
Cross-check claimed venues in the .bib against dblp keys / USENIX URLs grep -E '^@' paper.bib | wc -l # inventory grep -A3 -iE 'booktitle.*(nsdi|sigcomm|osdi|sosp)' paper.bib | head -40 For each NSDI claim: the usenix.org/conference/nsdi<yy>/presentation/<key> page or the dblp record must exist. No render, no citation-as-NSDI.
What does the nsdi-related-work skill do?
Use 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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-related-work --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.