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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-related-work --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | | Defenses your attack bypasses / attacks your defense stops | Both academic and *deployed* (vendor advisories, OS release notes) | Ignoring deployed mitigations reviewers run daily | | Measurement baselines | PAM/IMC + the flagships | Claiming novelty for a re-measurement | The staggered-deadline effect: by any S&P cycle's close, the previous USENIX Security and CCS programs are public. Reviewers wil
- The coverage lanes an Oakland reviewer checks
- Positioning is a delta statement, not a list
- Concurrent work and arXiv
- The 40% rule creates a disclosure duty
- Verify venue attribution before citing
- Anonymous self-citation discipline
- Output format
For each load-bearing citation:
curl -s "https://dblp.org/search/publ/api?q=<title>&format=json" | jq '.result.hits.hit[].info | {title, venue, year}'What does the ieeesp-related-work skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-related-work --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.