sosp-related-work
Use when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing, third-person self-citation under double-blind rules, and handling concurrent work across the now-annual systems deadline circuit.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-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.
# SOSP Related Work Use this when writing or auditing the related-work section of a SOSP paper. At this venue the section is a load-bearing wall: the PC contains authors of the systems you must compare against, the meeting will replay any positioning gap out loud, and the "how does this differ from X" review is the most common avoidable negative. Rules below reflect the 2026-cycle CFP's double-blind policy (checked 2026-07-08). ## Know the lineage or be corrected in public A SOSP reviewer expects the paper to place itself in the SOSP/OSDI line of work on its problem — often decades deep — plus the adjacent venues where the problem also lives (EuroSys, USENIX ATC, NSDI for networked systems, FAST for storage, ASPLOS at the architecture boundary). Two search passes are mandatory before the freeze: 1. **Ancestry pass**: walk the problem back through prior SOSP/OSDI editions via `dl.acm.org/conference/sosp`, dblp, and the SIGOPS Hall of Fame list (`sigops.org/awards/hof/`) — a HoF paper on your problem uncited is a credibility wound out of proportion to its citation value. 2. **Recency pass**: both SOSP and OSDI have run annually since 2024, so the "last edition" is now at most a year
- Know the lineage or be corrected in public
- Compare structures, not abstracts
- Double-blind mechanics in the citations
- Concurrent work across an annual circuit
- Placement and length
- Output format
What does the sosp-related-work skill do?
Use when positioning a SOSP submission against the systems literature — the SOSP/OSDI lineage a PC expects you to know, structural comparison instead of citation listing, third-person self-citation under double-blind rules, and handling concurrent work across the now-annual systems deadline circuit.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-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 984 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.