Individual skill

ieeesp-related-work

Use when positioning an IEEE S&P (Oakland) paper against prior literature, including coverage across the four security flagships, concurrent-work and arXiv norms, the 40% resubmission-overlap disclosure, verifying venue attribution via dblp and IEEE Xplore, and anonymity-safe self-citation.

IEEE-SP-Skills/skills/ieeesp-related-work/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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,410
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# IEEE S&P Related Work

Use this when building the positioning sections. Security literature is
scattered across four flagship conferences with staggered deadlines, so
"prior work" at S&P means a moving window across venues — and the PC
contains authors of the papers you are positioning against.

## The coverage lanes an Oakland reviewer checks

| Lane | Where it lives | Typical miss |
|---|---|---|
| Same attack/defense family | S&P, USENIX Security, CCS, NDSS — last ~3 years of each | Citing only "your" flagship |
| The system/protocol being attacked | Its home community (systems, networking, ML, crypto venues) | Attacking a strawman version already fixed upstream |
| Prior SoKs of the area | S&P especially (SoK lane since 2010) | Re-taxonomizing without citing the existing taxonomy |
Back to top