nsdi-author-response
Use when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the submission when no response phase exists.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-author-response --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 Author Response At NSDI the author's voice reaches reviewers at two moments only: inside the original submission, and — if granted — inside a one-shot revision packet read by the same people who wrote the demands. There is no rendered rebuttal phase in the '27 CFP (absence 待核实; verify each cycle). This skill covers both moments; the second is the venue's signature mechanism and the reason this skill is not a rebuttal-writing guide. ## Moment one: the response you embed in advance Without a mid-review channel, anticipated objections must be answered in the PDF: - Run the objection drill: each coauthor writes the three most likely reviewer complaints; any complaint appearing twice gets a paragraph in the paper — typically a "why not X?" design-alternatives note or a limits paragraph (`nsdi-writing-style`). - Pre-empt the baseline attack by documenting baseline tuning in-body (`nsdi-experiments`). - Pre-empt the scope attack with an explicit sentence locating the contribution in the networking stack or distributed design (`nsdi-topic-selection`). ## Moment two: the one-shot revision, treated as a contract The decision letter's required-issues list is an offer with exact terms:
- Moment one: the response you embed in advance
- Moment two: the one-shot revision, treated as a contract
- The packet: memo + highlighted diff
- Timeline for a typical revision window
- When the letter says plain reject
- Output format
What does the nsdi-author-response skill do?
Use when answering NSDI reviewers through the channel the venue actually provides — executing a one-shot revision against the required-issues list, writing the change memo and highlighted diff for the same reviewers, and pre-empting objections inside the submission when no response phase exists.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-author-response --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.