菜单
Use when positioning an NDSS submission against prior literature — sweeping the security big four plus the specialist venues, writing precise deltas, verifying every citation against NDSS's open proceedings and dblp, and keeping self-reference double-blind.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/brycewang-stanford/Awesome-Journal-Skills --skill ndss-related-work命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready through ACL Anthology publication.
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.
基于 SOC 职业分类
正在显示 SKILL.md
| name | ndss-related-work |
| description | Use when positioning an NDSS submission against prior literature — sweeping the security big four plus the specialist venues, writing precise deltas, verifying every citation against NDSS's open proceedings and dblp, and keeping self-reference double-blind. |
At NDSS the related-work section is a security argument: it establishes that the adversary, the precondition, or the defense you present is genuinely new at the layer you claim. The worked example in this pack turns on exactly that move — separating delegation-layer staleness from well-known record-layer takeover. Aim your section at the same standard: distinguish by mechanism, not by adjective.
| Tier | Venues / sources | What you owe them |
|---|---|---|
| Flagships | NDSS, IEEE S&P, USENIX Security, CCS (last ~3-4 years) | The nearest neighbors and your delta against each |
| Specialists | PETS, IMC, ACSAC, RAID, EuroS&P, WOOT | Depth in your sub-area; measurement lineage |
| Co-located ecosystem | NDSS workshops (e.g., BAR, USEC, MADWeb — 2026 list verified) | Early-stage versions of your idea often surface here first |
| Non-academic record | CVEs, vendor advisories, IETF drafts/RFCs, incident writeups | Whether practitioners already know your "novel" issue |
| Preprints | arXiv (cs.CR), IACR ePrint | Concurrent work; cite, date, and differentiate |
The non-academic tier is the one academic drafts skip and security reviewers do not: an attack already described in a vendor advisory or an RFC's security considerations is not novel because no PDF said it.
A delta sentence names the prior work's mechanism, states yours, and locates the difference in adversary, layer, precondition, or guarantee:
One such sentence per genuine neighbor beats a paragraph of citation carpet. Group the rest by theme with one honest line each.
NDSS's own proceedings are free — there is no paywall excuse for citing from memory.
For each citation:
1. Resolve it: ndss-symposium.org proceedings page, dblp (conf/ndss,
conf/uss, conf/sp, conf/ccs...), or DOI (NDSS uses 10.14722/NDSS.*).
2. Confirm venue + year + author list against the resolved record —
security classics are chronically misattributed across the big four
(see the checked list in ../../resources/exemplars/library.md).
3. Confirm the claim you attribute actually appears in the paper, not
in its folklore.
4. Cite the archival version over the preprint when both exist.
If a fetch is blocked (this pack's own source map documents 403s from ndss-symposium.org
and dblp.org in some environments), verify through search renderings of the exact URL and
note what could not be confirmed instead of guessing.
The 2027 CFP mandates anonymized submissions. For your own prior work:
The dual-cycle structure means near-identical ideas surface months apart. If a concurrent paper appears (arXiv, another venue's acceptance list) before your deadline: cite it, date both efforts, and write the technical difference plainly. Reviewers at this venue routinely review for the sibling conferences in the same season — assume they have seen the concurrent paper even if you had not.
Related work at NDSS commonly closes the paper (before conclusion) when the introduction already carries the sharp deltas, or follows the introduction when the field is crowded and positioning is the contribution's fulcrum. Either way it draws from the same 13-page budget: roughly one page, spent on differentiation rather than survey. A tutorial of the area belongs in background, and only if the design needs it.
[Neighbor map] nearest 3-6 works, each with a mechanism-level delta sentence
[Coverage gaps] tiers with no citations (flagship / specialist / advisory / preprint)
[Attribution audit] citations verified N/M; failures listed with resolution
[Anonymity leaks] first-person self-references or fingerprinting labels found
[Concurrent-work plan] known concurrent efforts + how the text handles them