osdi-related-work
Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-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.
# OSDI Related Work Position the paper the way a systems PC checks it. The anonymity mechanics referenced here are OSDI '26 rules (verified 2026-07-08); the literature lanes are structural and change slowly, but the nearest-neighbor papers change every cycle. ## What related work does at OSDI An OSDI related-work section is not a survey; it is a **difference ledger**. For each neighboring system: what it does, what it cannot do that yours can, and *why* — at the mechanism level. Systems reviewers usually know the neighbors personally; they are not reading to learn the area but to test whether you know exactly where you sit. The strongest form is one sentence of grouping plus one sentence of mechanism-level difference per group, with the difference tied to your design's named idea (see `osdi-writing-style`). "Unlike X, we are faster" is not a difference; "X orders its log cluster-wide, so its recovery scope is the cluster; ours is the tenant" is. ## The six lanes to sweep | Lane | Where it lives | What reviewers check | |---|---|---| | Direct competitors | Recent OSDI/SOSP programs | Is the nearest published system compared head-on, in the evaluation and not only in prose? | | The s
- What related work does at OSDI
- The six lanes to sweep
- USENIX open access is a verification tool
- Citing yourself under OSDI '26 anonymity
- Difference-ledger template
- Failure patterns PCs flag
- Neighbors that exist only on arXiv
- Output format
Venue sanity pass over the bibliography (run before the anonymity sweep) grep -nEi 'booktitle.*(OSDI|SOSP|NSDI|FAST|EuroSys|ATC|Annual Technical)' refs.bib | sort | uniq -c | sort -rn For each OSDI-attributed entry: confirm a conf/osdi/ dblp key exists. For each ATC entry dated 2026+: USENIX ATC ended after ATC '25 — recheck the actual venue (successor is stewarded by ACM SIGOPS).
What does the osdi-related-work skill do?
Use when positioning an OSDI submission against prior systems literature — covering the OSDI/SOSP/NSDI/FAST/EuroSys/ATC lanes, verifying venues through USENIX's free open-access proceedings and dblp, and citing your own precursors without breaking the renamed-system anonymity rule.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-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.