nsdi-review-process
Use 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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-review-process --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 Review Process NSDI's review machinery differs from single-deadline conferences in one structural way: decisions are moves in a multi-deadline game, not endpoints. Reading a decision letter correctly requires knowing which moves it opens and which it closes. Mechanics below are the NSDI '27 CFP and the NSDI '26 multiple-deadlines page as rendered on 2026-07-08. ## Pipeline shape Each deadline (spring, fall) runs its own double-blind PC review on its own HotCRP site, producing its own decision cohort — NSDI even publishes per-cohort accepted-paper lists before the symposium. Within a cohort: - Reviews are written against the paper as submitted; the rendered '27 CFP describes **no author-response phase** between reviews and decisions (absence 待核实 — check the current cycle's pages before relying on it). Plan as if the submission must argue for itself (`nsdi-author-response`). - Review loads are bounded upstream by the **eight-submissions-per-author cap**, which exists to protect PC bandwidth — expect enforcement, not flexibility. - Notifications land on published dates: July 23, 2026 for '27 spring; December 8, 2026 for '27 fall. ## The three-way outcome space | Decision | What
- Pipeline shape
- The three-way outcome space
- What reviewers reward and punish
- Decoding common letters
- Ban arithmetic, worked
- Signals to mine from the reviews themselves
- Confidentiality and conduct
- Output format
What does the nsdi-review-process skill do?
Use 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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-review-process --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.