nsdi-workflow
Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-workflow --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 Workflow NSDI is a calendar problem disguised as a conference. One edition, two submission gates, two decision cohorts, and a revision mechanism that spans deadlines — a team that plans "for NSDI" without naming the gate usually discovers it planned for neither. Dates below are the NSDI '27 cycle as rendered on 2026-07-08; treat them as this cycle's snapshot and re-pull the HotCRP `/deadlines` pages before acting. ## The '27 clock | Gate | Date (11:59 pm US EDT) | Cohort | |---|---|---| | Spring abstracts | April 16, 2026 | spring | | Spring full papers | April 23, 2026 | spring | | Spring notification | July 23, 2026 | spring | | Fall abstracts | September 10, 2026 | fall | | Fall full papers | September 17, 2026 | fall | | Fall notification | December 8, 2026 | fall | | Symposium | May 11-13, 2027, Providence, RI | both | Where "today" (2026-07-08) sits: spring authors are two weeks from notification; a fresh submission has nine weeks to the fall abstract gate. Camera-ready dates and the '27 artifact schedule were not yet rendered — 待核实, watch the conference page. ## One project, four legal paths through the cycle ```text Path A fall '26 submit -> accept (Dec 8) -> final p
- The '27 clock
- One project, four legal paths through the cycle
- Working backward from a gate
- The waits, and what to do inside them
- Revision-window management (path B/D)
- Choosing between the gates when both are open
- Standing risks with named owners
- Output format
What does the nsdi-workflow skill do?
Use when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-workflow --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.