TransformerLens Interpretability
Orchestra-Research/AI-Research-SKILLs
Guides mechanistic interpretability work with TransformerLens: loading models, caching activations, using HookPoints, activation patching and attention-pattern analysis.
A skill your agent uses when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the…
MITAuto-check passed
Install Ndss Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-review-process --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-review-process .claude/skills/ndss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-review-process into .claude/skills/ndss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-review-process --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-review-process .agents/skills/ndss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-review-process into .agents/skills/ndss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-review-process --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-review-process .cursor/skills/ndss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-review-process into .cursor/skills/ndss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-review-process --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-review-process .gemini/skills/ndss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-review-process into .gemini/skills/ndss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/ndss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-review-process into .github/skills/ndss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/ndss-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-review-process into .opencode/skills/ndss-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 605 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the…
- Interpreting where an NDSS submission stands — the two-round pipeline inside each cycle
- SKILL.md covers The pipeline (2027 cycle…, What each outcome means, Round 1: what the breadth read… and Round 2: where papers are…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The early reject with Round-1 reviews
What it does
Ndss Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the Accept / Minor Revision / Major Revision decision set, and the Ethics Review Board's role.
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
- Interpreting where an NDSS submission stands — the two-round pipeline inside each cycle
- The early reject with Round-1 reviews
- Rebuttal and interactive discussion
- The Accept / Minor Revision / Major Revision decision set
Example prompts
- “/ndss-review-process”
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 Review Process loads about 1.3k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 605 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). 605 words, ~1,340 tokens.
Download SKILL.mdSave it as
.claude/skills/ndss-review-process/SKILL.md (or your agent's skills folder).- name
- ndss-review-process
- description
- Use when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the Accept / Minor Revision / Major Revision decision set, and the Ethics Review Board's role.
NDSS Review Process
Each NDSS cycle is a funnel with one public narrowing: Round 1 reads everything and ejects the bottom; Round 2 argues about the rest. Knowing which stage you are in — and what each stage can still change — prevents both wasted effort and missed leverage.
The pipeline (2027 cycle structure, verified 2026-07-08)
submit ──▶ ROUND 1 (breadth read)
│
├─ early reject ──▶ Round-1 reviews released; cycle over for this paper;
│ major-overlap resubmission barred within this
│ symposium's other cycle
│
└─ continue ──▶ ROUND 2 (depth read, more reviewers/discussion)
│ rebuttal + interactive discussion with reviewers
▼
Accept │ Minor Revision │ Major Revision │ RejectDates for the fall cycle: early notification September 25, rebuttal and discussion October 8-10, final decision November 4, 2026. The summer cycle followed the same shape (June 12 / June 24-28 / July 22).
What each outcome means
| Outcome | Substance | Author obligation |
|---|---|---|
| Accept | Paper in, Seoul slot earned | Camera-ready by Jan 6, 2027; consider artifact evaluation |
| Minor Revision | Accepted contingent on a bounded fix-up judged satisfactory | Execute exactly the requested changes, promptly |
| Major Revision | Promising but incomplete — new experiments, implementations, or proofs required | Resubmit within the stated window against a written list of revision tasks; re-review checks task fulfillment; at most one major revision per paper |
| Early reject / Reject | Out for this edition | Fold reviews in; retarget (see ndss-workflow) |
The Major Revision list is the closest thing conference review offers to a contract: the original reviewers wrote the tasks, and the resubmission is judged against them — not against fresh whims. Treat each task as a deliverable with evidence; treat silence on a task as a decline you must justify explicitly.
Round 1: what the breadth read screens for
Round-1 reviewers triage many papers quickly. They are deciding whether further review is worth the PC's time, which concentrates attention on: an intelligible threat model, a believable evidence type for the claim category, obvious scope or novelty problems, ethics red flags, and format/anonymity violations. The writing-style skill's first-page contract is calibrated to exactly this read. An early reject is not an insult; it is a verdict that the fast read failed — often fixable, but not this edition.
Round 2: where papers are actually won
Round 2 adds closer reads and a live element: authors see reviews, respond, and then
interact with reviewers during a discussion phase. Decisions crystallize here through
reviewer-to-reviewer argument. Your rebuttal's real audience is the undecided reviewer
and the discussion that follows it (tactics in ndss-author-response). Reviews that
misread the paper are, at this stage, evidence about the paper: something on the page let
the misreading happen.
Show full SKILL.md (225 more words)Show less
The Ethics Review Board
Any reviewer can flag a submission as ethically fraught; flagged papers get examined by an ERB drawn from the TPC. It evaluates harm handling against community norms (the Menlo Report is the CFP's named reference), and its judgment can override technical enthusiasm. Papers are not penalized for doing dangerous-looking research — they are penalized for doing it without visible reasoning about harm, consent, and disclosure. The ERB reads the Ethics Considerations section as your testimony; write it before submission as if the board were guaranteed to convene.
Confidentiality and conduct
Reviews, scores, and discussion content are confidential; do not quote them publicly, and do not attempt out-of-band contact with suspected reviewers — chairs are the only channel. Public preprints are a separate question (check the current CFP's stance) but engaging with reviewers about the paper anywhere except HotCRP is a bright line at every security flagship.
Reading your reviews diagnostically
- All reviewers stumble at the same section → structural problem there, not reviewer error.
- Scores split wide → the paper supports two readings; the rebuttal must collapse the wrong one with pointable evidence.
- "Threat model unrealistic" → either defend the model's real-world instantiation with named deployments, or the topic-selection test was failed months ago.
- Every weakness listed is fixable-in-weeks → a Major Revision may be within reach; make the fixes look scoped in your response.
Output format
[Stage] round-1 pending / round-2 / decided: <outcome>
[Cycle dates] next milestone + days remaining
[Review diagnosis] convergent objections, split points, misreadings
[ERB exposure] flagged risk areas + where the paper answers them
[Next action] rebuttal / revision-task plan / retarget, with owner© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ndss Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| TransformerLens InterpretabilityOrchestra-Research/AI-Research-SKILLs | 13k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Nnsight Remote InterpretabilityOrchestra-Research/AI-Research-SKILLs | 13k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 | |
| Round VerificationSeemSeam/claude_codex_bridge | 3.6k | — | ~228 | Automated safety check: Pass | Custom licence | |
| Round VerificationSeemSeam/claude_codex_bridge | 3.6k | — | ~486 | Automated safety check: Pass | Custom licence |
Similar skills
Nnsight Remote Interpretability
Orchestra-Research/AI-Research-SKILLs
Provides guidance for interpreting and manipulating neural network internals using nnsight with optional NDIF remote execution.
Paper Interpretation
digoal/blog
从论文 PDF 文件或论文 PDF URL 生成通俗易懂、图文并茂、带批判性评估的中文 Markdown 解读，并保存到当前项目的 markdown 目录。Use when the user asks to interpret,精读,解读,summarize,explain,analyze, or write an article from an academic paper PDF…
Round Verification
SeemSeam/claude_codex_bridge
Verify a CCB execution round and produce a machine-readable round result artifact.
Round Verification
SeemSeam/claude_codex_bridge
Verify integrated round evidence and return a machine-readable round result for script import.
Implementing Zero Standing Privilege With Cyberark
mukul975/Anthropic-Cybersecurity-Skills
Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time…
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 Review Process
What does Ndss Review Process do?
A skill your agent uses when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the…. Ndss Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when interpreting where an NDSS submission stands — the two-round pipeline inside each cycle, the early reject with Round-1 reviews, rebuttal and interactive discussion, the Accept / Minor Revision / Major Revision decision set, and the Ethics Review Board's role.
When should I use Ndss Review Process?
Ndss Review Process fits situations like: interpreting where an NDSS submission stands — the two-round pipeline inside each cycle; the early reject with Round-1 reviews; rebuttal and interactive discussion; the Accept / Minor Revision / Major Revision decision set.
How do I install Ndss Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-review-process -a claude-code`. Or copy the skill folder (NDSS-Skills/skills/ndss-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ndss-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Ndss Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-review-process -a codex`. Or copy the skill folder (NDSS-Skills/skills/ndss-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ndss-review-process in your project. Codex loads it when a task matches its description.
Can I use Ndss Review Process 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-review-process -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-review-process, .gemini/skills/ndss-review-process, .github/skills/ndss-review-process and .opencode/skills/ndss-review-process in your project.
What does Ndss Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Ndss Review Process is instructions for the agent only.
Does Ndss Review Process 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 Review Process 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 Review Process use?
Ndss Review Process 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 Review Process 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 Review Process?
Skills that share tags, products or a category with Ndss Review Process: TransformerLens Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Nnsight Remote Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Paper Interpretation (digoal/blog, 8.6k stars) and Round Verification (SeemSeam/claude_codex_bridge, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ndss Review Process?
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.