nsdi-submission
Use 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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-submission --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 Submission The audit below is ordered by irreversibility: calendar errors first, then format, then blindness, then policy. Numbers are the NSDI '27 cycle as rendered on 2026-07-08; the fall HotCRP `/deadlines` page outranks everything here. ## Gate 0: the right site, the right clock NSDI runs a **separate HotCRP instance per deadline** (`nsdi27spring.usenix.hotcrp.com`, `nsdi27fall...`). Uploading to a stale spring site bookmarked in March is a real failure mode. For the '27 fall gate: - Abstracts (title, author list, track, conflicts): **September 10, 2026**. - Full papers: **September 17, 2026**. - Both **11:59 pm US EDT** — an Eastern-US midnight, not AoE and not the Pacific cutoff NSDI '26 used. Same-named deadlines moved time zones between editions; compute each coauthor's local equivalent from the HotCRP page, not from memory. The abstract gate is a prerequisite: no registered abstract, no paper upload a week later. Register even if 60% sure — withdrawing is free, materializing an unregistered paper is impossible. ## Gate 1: format | Item | '27 rule | Audit action | |---|---|---| | Body | ≤ 12 pages incl. footnotes, figures, tables | Count on the compiled PDF | | Refer
- Gate 0: the right site, the right clock
- Gate 1: format
- Gate 2: blindness, per track
- Gate 3: policy
- HotCRP form fields deserve the same audit as the PDF
- Final sequence
- Output format
Mechanical pass on the exact upload candidate pdftotext final.pdf - | grep -nEi '(acknowledg|funded by|grant|@[a-z]+\.(com|edu))' | head pdfinfo final.pdf | grep -Ei 'author|creator' # PDF metadata identity grep -rnEi '(github\.com/[a-z0-9-]+|/home/|/Users/)' *.tex figures/ | head research track only: search for your institution's giveaway nouns pdftotext final.pdf - | grep -niE 'ourcorp|internal-codename' | head
What does the nsdi-submission skill do?
Use 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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-submission --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.