sigcomm-related-work
Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-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.
# SIGCOMM Related Work Use this to audit novelty and placement. SIGCOMM is the broad networking flagship, so a paper is read against the strongest prior work in its exact subarea — and against results scattered across sibling venues. Reopen the current CFP for concurrent-submission and anonymity rules before advising. ## Positioning checks - Separate the **mechanism** you contribute from engineering polish: a new protocol, transport signal, forwarding architecture, measurement-driven design, or programmable-data-plane technique. - Sweep the whole networking literature, not just SIGCOMM: the nearest prior work may sit in NSDI, MobiCom, CoNEXT, IMC, SIGMETRICS, INFOCOM, or a journal like IEEE/ACM Transactions on Networking. A bibliography that cites only SIGCOMM signals a narrow read. - **Prove each placement.** Verify the venue and year on dblp and the ACM DL before you assert it; do not rely on memory for where a famous result appeared. - Distinguish **main-track proceedings** from **CCR editorial notes** — OpenFlow's famous CCR note is not a SIGCOMM conference paper, and citing it as one is a checkable error. - Handle concurrent and prior versions honestly, and keep every self-cit
- Positioning checks
- Venue-coverage table
- The misattribution guard
- Positioning vignette
- Concurrent-work judgment calls
- Output format
What does the sigcomm-related-work skill do?
Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-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.