nsdi-topic-selection
Use 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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-topic-selection --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 Topic Selection Venue choice at NSDI is a scope question before it is a quality question. The notes below reflect the NSDI '27 Call for Papers as rendered on 2026-07-08; the scope paragraph, track list, and exclusions are rewritten each edition, so reread `usenix.org/conference/nsdi27/call-for-papers` before committing a team to a deadline. ## The scope sentence that decides most cases The CFP's negative space is unusually explicit. Three families are declared out of scope regardless of quality: 1. Work with **no contribution to the design of networked systems or the networking stack** — a distributed application that merely *uses* the network is not enough. 2. **Hardware architecture** and **physical-layer** contributions (beamforming, modulation, and similar). 3. **Sensing and localization** work. The positive test is the venue's full name: design principles, implementation, and **practical evaluation** of networked and distributed systems. Ask: *which layer of a networked system does this change, and what realistic traffic has been pushed through the change?* If neither clause has an answer, no amount of polish fixes the fit. ## Three tracks, three evidence contracts NSDI
- The scope sentence that decides most cases
- Three tracks, three evidence contracts
- Routing among the siblings
- Calendar as a routing input
- Borderline cases, adjudicated
- Fit probes before committing a deadline
- Output format
What does the nsdi-topic-selection skill do?
Use 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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-topic-selection --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.