Individual skill

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.

NSDI-Skills/skills/nsdi-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,397
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top