Deadlines
anthropics/claude-for-legal
Track case deadlines — add, cross-case rollup report, update, complete, close.
A skill your agent uses when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline…
MITAuto-check passed
Install Nsdi Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-review-process .claude/skills/nsdi-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 "nsdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-review-process into .claude/skills/nsdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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/NSDI-Skills/skills/nsdi-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 nsdi-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-review-process .agents/skills/nsdi-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 "nsdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-review-process into .agents/skills/nsdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-review-process .cursor/skills/nsdi-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 "nsdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-review-process into .cursor/skills/nsdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 NSDI-Skills/skills/nsdi-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 nsdi-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-review-process .gemini/skills/nsdi-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 "nsdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-review-process into .gemini/skills/nsdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-review-process .github/skills/nsdi-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 "nsdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-review-process into .github/skills/nsdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-review-process .opencode/skills/nsdi-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 "nsdi-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-review-process into .opencode/skills/nsdi-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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
nsdi-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 655 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 NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline…
- Interpreting where an NSDI submission stands — the per-deadline PC pipeline
- SKILL.md covers Pipeline shape, The three-way outcome space, What reviewers reward and punish and Decoding common letters, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The three-way outcome space of accept
What it does
Nsdi Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline resubmission ban, reviewer continuity across revisions, and what each decision letter actually commits the authors to.
Its SKILL.md is about 1.6k 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 NSDI submission stands — the per-deadline PC pipeline
- The three-way outcome space of accept
- One-shot revision
- The cross-deadline resubmission ban
Example prompts
- “/nsdi-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
Nsdi Review Process loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 655 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). 655 words, ~1,559 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-review-process/SKILL.md (or your agent's skills folder).- name
- nsdi-review-process
- description
- Use when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline resubmission ban, reviewer continuity across revisions, and what each decision letter actually commits the authors to.
NSDI Review Process
NSDI's review machinery differs from single-deadline conferences in one structural way: decisions are moves in a multi-deadline game, not endpoints. Reading a decision letter correctly requires knowing which moves it opens and which it closes. Mechanics below are the NSDI '27 CFP and the NSDI '26 multiple-deadlines page as rendered on 2026-07-08.
Pipeline shape
Each deadline (spring, fall) runs its own double-blind PC review on its own HotCRP site, producing its own decision cohort — NSDI even publishes per-cohort accepted-paper lists before the symposium. Within a cohort:
- Reviews are written against the paper as submitted; the rendered '27 CFP describes
no author-response phase between reviews and decisions (absence 待核实 — check
the current cycle's pages before relying on it). Plan as if the submission must
argue for itself (
nsdi-author-response). - Review loads are bounded upstream by the eight-submissions-per-author cap, which exists to protect PC bandwidth — expect enforcement, not flexibility.
- Notifications land on published dates: July 23, 2026 for '27 spring; December 8, 2026 for '27 fall.
The three-way outcome space
| Decision | What it means | What it opens / closes |
|---|---|---|
| Accept | into the cohort's program | final paper, artifact evaluation, presenter duties |
| One-shot revision | conditional path: reviewers issue a list of required issues | resubmit at a subsequent deadline (possibly next year's NSDI); same reviewers where possible; one attempt |
| Reject | out, with a ban attached | cannot enter the next deadline; spring reject skips same-edition fall, fall reject skips next edition's spring |
The one-shot revision is neither a rebuttal nor journal-style R&R-until-done. Its grammar: the reviewers' issue list is exhaustive and binding; the revision is judged on whether those issues are fixed; a revision that dodges them is rejected without another revision option. Institutional continuity is built in — the same reviewers re-review where possible, and PC members who issue one-shot revisions at a fall deadline are required to serve as external reviewers the following year, so the issue list is written by people expecting to check it.
What reviewers reward and punish
Reading NSDI reviews (and pre-empting them) is easier with the venue's evaluative axes explicit:
- Design contribution to networked systems or the stack — the scope clause
functions as review criterion; "solid work, wrong venue" is a real NSDI outcome
(
nsdi-topic-selection). - Practical evaluation — trace realism, incumbent baselines, tail visibility
(
nsdi-experiments). - Honesty about limits — named failure regimes read as strength.
- Track-contract fulfillment — operational papers judged on depth of deployed experience; frontiers papers on boldness and framing rather than completeness.
Show full SKILL.md (252 more words)Show less
Decoding common letters
"One-shot revision. Required: (1) compare against <deployed system>;
(2) evaluate under churn; (3) clarify lease-expiry semantics."
-> A funded offer. Cost it (~2 machine-months + rewrite), reserve the
testbed now, target the named next deadline. Success odds are good
*because* the same reviewers check their own list.
"Reject. The contribution is an application of known techniques; the
networking stack is unchanged."
-> Scope verdict, not effort verdict. Re-route (SIGCOMM? OSDI?) or
re-center the design contribution. Ban: skip one NSDI deadline.
"Reject. Evaluation limited to microbenchmarks on a two-node setup."
-> Evidence-rung verdict. The ban window is exactly the time to climb
a rung (trace replay, scale-out) before the after-next deadline.Ban arithmetic, worked
A paper rejected at fall '26 (notified December 9, 2025 — the '26-cycle dates)
could not enter spring '27 (April 2026) and became eligible again at fall '27
(September 2026). Generalize: a plain rejection costs one deadline ≈ 5 months of
eligibility, which is precisely why nsdi-workflow treats speculative submissions
as spending a real option, and why the strongest response to a borderline draft is
often holding it one gate.
Signals to mine from the reviews themselves
Whatever the outcome, NSDI reviews carry venue-calibrated information worth extracting systematically:
- Which track bar was applied — reviews that fault a research-track paper for missing deployment experience (or vice versa) reveal a track mismatch to fix before any resubmission.
- Which baseline the community considers canonical — a named "why not X?" defines the comparison the next version cannot skip.
- Repeated confusion across reviewers — two reviewers misreading the same
mechanism marks a writing defect, not two reading defects
(
nsdi-writing-style). - The evidence rung the scores imply — enthusiasm plus low confidence often
means the idea landed but the evaluation did not reach the rung the claim needs
(
nsdi-experiments).
Confidentiality and conduct
Reviews and PC deliberations are confidential; submissions are read under double-blind rules with declared conflicts recused via HotCRP. Do not contact PC members about a pending paper; process questions go to the program co-chairs (named on the current conference page; the '27 pair 待核实). Decisions are not relitigated by email — the sanctioned channel for disagreement is the revision or the next eligible submission.
Output format
[Cohort] spring/fall + year; notification date; days remaining
[Outcome] accept / one-shot revision / reject
[If revision] issue list -> cost -> feasible target deadline
[If reject] ban window (dates); scope vs evidence diagnosis; re-route call
[Reviewer continuity] same-reviewer expectations affecting strategy
[Next action] single highest-leverage step, dated© 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 NSDI-Skills/skills/nsdi-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi 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 |
|---|---|---|---|---|---|---|
| Nsdi Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Deadlinesanthropics/claude-for-legal | 9.6k | 3 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| 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 | |
| Deadline Funnel AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~760 | Automated safety check: Pass | None | |
| Paper Interpretationdigoal/blog | 8.6k | — | ~1.5k | Automated safety check: Pass | GPL-2.0 |
Similar skills
- Official
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.
Nnsight Remote Interpretability
Orchestra-Research/AI-Research-SKILLs
Provides guidance for interpreting and manipulating neural network internals using nnsight with optional NDIF remote execution.
Deadline Funnel Automation
ComposioHQ/awesome-claude-skills
Automate Deadline Funnel tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
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…
Deadline Prep
davila7/claude-code-templates
Generate a structured demo outline from your session's change log and git history.
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 Nsdi Review Process
What does Nsdi Review Process do?
A skill your agent uses when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline…. Nsdi Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when interpreting where an NSDI submission stands — the per-deadline PC pipeline, the three-way outcome space of accept, one-shot revision, and reject, the cross-deadline resubmission ban, reviewer continuity across revisions, and what each decision letter actually commits the authors to.
When should I use Nsdi Review Process?
Nsdi Review Process fits situations like: interpreting where an NSDI submission stands — the per-deadline PC pipeline; the three-way outcome space of accept; one-shot revision; the cross-deadline resubmission ban.
How do I install Nsdi Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-review-process -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-review-process -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-review-process in your project. Codex loads it when a task matches its description.
Can I use Nsdi 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 nsdi-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/nsdi-review-process, .gemini/skills/nsdi-review-process, .github/skills/nsdi-review-process and .opencode/skills/nsdi-review-process in your project.
What does Nsdi Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Nsdi Review Process is instructions for the agent only.
Does Nsdi 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 Nsdi 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 Nsdi Review Process use?
Nsdi 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 Nsdi Review Process use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 Nsdi Review Process?
Skills that share tags, products or a category with Nsdi Review Process: Deadlines (anthropics/claude-for-legal, 9.6k stars), TransformerLens Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars), Nnsight Remote Interpretability (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Deadline Funnel Automation (ComposioHQ/awesome-claude-skills, 77k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi 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.