socc-related-work
Use when positioning an ACM SoCC submission against both the systems literature (OSDI, NSDI, EuroSys, ATC, SOSP, SoCC) and the data-management literature (SIGMOD, VLDB), writing delta-first contrast rather than a citation catalog, keeping self-citations dual-anonymous, and handling concurrent, preprint, and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.
# SoCC Related Work Use this to audit novelty and eligibility. SoCC reviewers come from **both SIGMOD and SIGOPS**, so a credible related-work section reaches **both** lanes — the systems flagships and the data-management flagships — and states where your paper sits relative to the nearest prior work as a **delta**, not a list. A bibliography that cites only one community tells a reviewer from the other that the paper may be a visitor. Reopen the current call for dual-submission, anonymity, and prior-publication rules before advising authors. ## Positioning checks - **Separate the cloud novelty from the engineering effort.** What is new: a mechanism, a measurement, a benchmark, a deployment lesson, or a cost model — and is it new to *both* communities or only one? - **Cover both lanes.** SoCC reviewers expect the systems venues (OSDI/NSDI/EuroSys/ATC/SOSP/SoCC) *and* the data venues (SIGMOD/VLDB) where relevant, not just the papers nearest your mechanism. - **Write delta-first.** Each closely related paper gets one sentence naming what it did and one naming what you do differently — not a summary. Position, don't catalog. - **Preserve dual anonymity.** Cite your own prior work in t
- Positioning checks
- Cloud literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the socc-related-work skill do?
Use when positioning an ACM SoCC submission against both the systems literature (OSDI, NSDI, EuroSys, ATC, SOSP, SoCC) and the data-management literature (SIGMOD, VLDB), writing delta-first contrast rather than a citation catalog, keeping self-citations dual-anonymous, and handling concurrent, preprint, and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.