ndss-author-response
Use when writing an NDSS rebuttal and working the interactive discussion phase — triaging Round-2 reviews under a short window, answering adaptive-attack and ethics objections with pointable evidence, and negotiating toward Accept or a well-scoped Minor/Major Revision.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-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.
# NDSS Author Response Reaching the rebuttal at NDSS already means something: the early reject did not take you, and the paper is in Round 2 with reviewers who will *talk back* — the 2027 process pairs the written response with an interactive discussion phase (fall window: October 8-10, 2026). Plan for a conversation, not a single volley. ## Triage first (day one of the window) Sort every review point into four buckets before writing a sentence: | Bucket | Test | Response strategy | | --- | --- | --- | | Misreading | The paper already answers it | Quote section/figure; ask implicitly "what would make this clearer?" | | Real gap, small | Answerable with existing data or a quick run | Present the number now; offer the camera-ready edit | | Real gap, large | Needs new experiments/implementation | Do not fake it — scope it as revision work; this is Major-Revision fuel, used well | | Judgment call | Reviewer weighs the contribution differently | One respectful paragraph on why the framing holds; then stop | Answer *every* reviewer, but spend the word budget where the decision is live: the skeptical-but-engaged review, not the enthusiast or the write-off. ## Rules of engagement - **Point
- Triage first (day one of the window)
- Rules of engagement
- The objections this venue actually raises
- Working the interactive discussion
- Skeleton
- Failure modes
- Output format
What does the ndss-author-response skill do?
Use when writing an NDSS rebuttal and working the interactive discussion phase — triaging Round-2 reviews under a short window, answering adaptive-attack and ethics objections with pointable evidence, and negotiating toward Accept or a well-scoped Minor/Major Revision.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-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.