nsdi-writing-style
Use when drafting or revising NSDI prose — building the operational-pain-to-design-principle arc, fitting argument and figures into 12 pages with references and appendices outside the cap, calibrating claims to trace and testbed evidence, and writing for reviewers who read tail percentiles before adjectives.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-writing-style --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 Writing Style An NSDI paper argues that a nameable design idea, embodied in a working networked system, holds up under realistic traffic. The prose exists to make that chain checkable. Format facts below are the NSDI '27 CFP as rendered on 2026-07-08. ## The opening arc NSDI first pages that work tend to execute five beats in order (see the rebuilt example in [`../../resources/worked-examples/01-introduction.md`](../../resources/worked-examples/01-introduction.md)): 1. **Operational pain, evidenced** — a failure shape, cost, or limit shown in a trace or deployment, not asserted from intuition. 2. **Why the networked setting causes it** — the distributed or stack-level reason local fixes fail. This beat is also the scope defense; a paper that cannot write it is drifting out of the CFP's "design of networked systems or the networking stack." 3. **The design principle, named** — the transferable idea, stated so another team could apply it to a different system. 4. **The built system** — what was implemented, where it runs, what was not built. 5. **Claims with evidence addresses** — each headline number tied to a section, a workload, and a percentile. ## Budget arithmetic before
- The opening arc
- Budget arithmetic before sentence polish
- Sentence-level calibration
- Anonymity constraints on prose
- Revision-letter prose (one-shot resubmissions)
- Figures as argument, not decoration
- Self-edit checklist
- Output format
What does the nsdi-writing-style skill do?
Use when drafting or revising NSDI prose — building the operational-pain-to-design-principle arc, fitting argument and figures into 12 pages with references and appendices outside the cap, calibrating claims to trace and testbed evidence, and writing for reviewers who read tail percentiles before adjectives.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-writing-style --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.