GSD Phase Discussion
open-gsd/gsd-core
Asks adaptive questions about a project phase and records the decisions in a CONTEXT.md that later research and planning agents can act on without asking again.
A skill your agent uses 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…
MITAuto-check passed
Install Ndss Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-author-response --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/NDSS-Skills/skills/ndss-author-response .claude/skills/ndss-author-response && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ndss-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-response into .claude/skills/ndss-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-author-response", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-responseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-author-response --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/NDSS-Skills/skills/ndss-author-response .agents/skills/ndss-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ndss-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-response into .agents/skills/ndss-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-author-response", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-author-response --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/NDSS-Skills/skills/ndss-author-response .cursor/skills/ndss-author-response && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ndss-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-response into .cursor/skills/ndss-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-author-response", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path NDSS-Skills/skills/ndss-author-response--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-author-response --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/NDSS-Skills/skills/ndss-author-response .gemini/skills/ndss-author-response && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ndss-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-response into .gemini/skills/ndss-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-author-response", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-author-responseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/NDSS-Skills/skills/ndss-author-response .github/skills/ndss-author-response && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ndss-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-response into .github/skills/ndss-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-author-response", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-author-response --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/NDSS-Skills/skills/ndss-author-response .opencode/skills/ndss-author-response && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ndss-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-author-response into .opencode/skills/ndss-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-author-response", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ndss-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 581 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Writing an NDSS rebuttal and working the interactive discussion phase — triaging Round-2 reviews under a short window
- SKILL.md covers Triage first (day one of the…, Rules of engagement, The objections this venue… and Working the interactive…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Answering adaptive-attack and ethics objections with pointable evidence
What it does
Ndss Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
- Negotiating toward Accept
- A well-scoped Minor/Major Revision
Example prompts
- “/ndss-author-response”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ndss Author Response loads about 1.3k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 581 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 581 words, ~1,339 tokens.
Download SKILL.mdSave it as
.claude/skills/ndss-author-response/SKILL.md (or your agent's skills folder).- name
- ndss-author-response
- description
- 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.
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, don't reargue. "Table 3, row 4 reports the adaptive variant: success drops to X% at cost Y" beats three paragraphs of prose. Every claim in the response should have a coordinate in the paper or a concrete new number.
- New results are allowed to be small. A single clarifying experiment run during the window, honestly labeled, moves discussions; a promised future experiment moves nothing.
- Concede precisely. "Correct — our measurement cannot distinguish A from B; we will weaken §5.2's claim accordingly" earns trust that the contested points then spend.
- Stay anonymous and in-channel. The response lives in HotCRP, double-blind rules still apply, and no external links that could fingerprint the authors.
Show full SKILL.md (295 more words)Show less
The objections this venue actually raises
"An adaptive attacker bypasses this." The highest-frequency defense-paper objection.
If the paper evaluated adaptation (ndss-experiments), point to it. If the reviewer's
specific strategy is genuinely new: analyze it in the response — capability check against
the threat model, then either an argument or a quick measurement. Never answer with "out
of scope" unless the threat model already excluded that capability in the submitted PDF.
"The ethics handling is insufficient." Respond with facts and dates, not reassurance: disclosure sent ⟨date⟩, vendor acknowledged ⟨date⟩, scan rate-capped at ⟨rate⟩ with opt-out honored, data handling per §Ethics. If the process moved since submission (a patch shipped, an advisory published), say so — it is among the few post-deadline facts reviewers welcome.
"Prevalence is overstated." Restate the population definition and validation, give the error directions, and if the reviewer is right that the sampled frame limits the claim, propose the exact weakened sentence for the camera-ready.
"Delta over [X] is thin." Answer at the mechanism level (layer, precondition, adversary), in two sentences, with a citation coordinate. Novelty debates are lost by volume and won by specificity.
Working the interactive discussion
The discussion phase rewards responsiveness: short turnaround, direct answers, no repetition of the written response. If a reviewer proposes a compromise reading ("the claim holds for provider-side deployments only"), engage with it seriously — discussions often converge on the Minor/Major Revision boundary, and a well-received author who scopes revisions crisply lands on the better side of it.
Skeleton
Thank-you line (one, no flattery).
COMMON THREADS (if ≥2 reviewers share an objection)
T1: <objection> → answer once, pointable evidence, camera-ready commitment.
REVIEWER A
A1 (misreading): see §4.1 ¶2 and Fig. 5; we will foreground this in §1.
A2 (small gap): ran the suggested configuration — result R; added to Tab. 2.
REVIEWER B
B1 (adaptive strategy S): S requires on-path capability; threat model §2
excludes it — but under S' (off-path variant) success is X% (new run).
...
REVISION OFFER (one block, scoped)
We commit to: [list]. We will not: [list, with one-line reasons].Failure modes
Rebuttals that rewrite the paper's argument from scratch; word budgets burned on the
strongest review; sarcasm at a misreading (misreadings are data — see
ndss-review-process); promising in the response what the revision cannot deliver, which
converts a winnable Major Revision into a failed one at re-review.
Output format
[Bucket map] each review point → misreading / small gap / large gap / judgment
[Live decision] which reviewer(s) the response must move, and with what
[New evidence] runs completed inside the window + where they land in the paper
[Revision offer] committed items vs declined items with reasons
[Discussion posture] open questions expected; owner for fast replies© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in NDSS-Skills/skills/ndss-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ndss Author Response next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ndss Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| GSD Phase Discussionopen-gsd/gsd-core | 10k | 1 repos | ~1.5k | Automated safety check: Warn | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Author Response Builderaipoch/medical-research-skills | 1.9k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Aistats Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~980 | Automated safety check: Pass | MIT | |
| Fast Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Author Response Builder
aipoch/medical-research-skills
Turns reviewer comments into structured, professional point-by-point responses linked to manuscript revisions, clarifications, rebuttals, and additional analyses.
Aistats Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting AISTATS author responses or author-reviewer discussion replies under OpenReview, covering text-only discussion, no-link guidance, no revised-paper upload…
Fast Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
Icassp Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Ndss Author Response
What does Ndss Author Response do?
A skill your agent uses 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…. Ndss Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Ndss Author Response?
Ndss Author Response fits situations like: 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; negotiating toward Accept; A well-scoped Minor/Major Revision.
How do I install Ndss Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a claude-code`. Or copy the skill folder (NDSS-Skills/skills/ndss-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ndss-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Ndss Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a codex`. Or copy the skill folder (NDSS-Skills/skills/ndss-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ndss-author-response in your project. Codex loads it when a task matches its description.
Can I use Ndss Author Response in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-author-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ndss-author-response, .gemini/skills/ndss-author-response, .github/skills/ndss-author-response and .opencode/skills/ndss-author-response in your project.
What does Ndss Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Ndss Author Response is instructions for the agent only.
Does Ndss Author Response access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ndss Author Response safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ndss Author Response use?
Ndss Author Response is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ndss Author Response use?
About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ndss Author Response?
Skills that share tags, products or a category with Ndss Author Response: GSD Phase Discussion (open-gsd/gsd-core, 10k stars), Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Author Response Builder (aipoch/medical-research-skills, 1.9k stars) and Aistats Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ndss Author Response?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.