Menu

Individual skill

sosp-related-work

0upvotes

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.

SOSP-Skills/skills/sosp-related-work/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
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.

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

# 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:
Back to top