Individual skill
ndss-related-work
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.
NDSS-Skills/skills/ndss-related-work/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- writing Derived category
- security Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# NDSS Related Work
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.
## Where NDSS reviewers expect you to have looked
| 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 |