infocom-related-work
Use when positioning an IEEE INFOCOM submission against the networking literature across INFOCOM, SIGCOMM, NSDI, MobiCom, ICNP, and the journals (IEEE/ACM ToN, IEEE JSAC/TMC), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind on EDAS, and handling concurrent, preprint, and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.
# INFOCOM Related Work Use this to audit novelty and eligibility. INFOCOM reviewers are close to the networking literature across both its analytical and systems wings, and they expect to see where your paper sits relative to the nearest prior work — stated as a **delta**, not a list. Reopen the current call for dual-submission, double-blind, and prior-publication rules before advising authors. ## Positioning checks - **Separate the networking novelty from the engineering effort.** What is new: a formulation, a bound/guarantee, a protocol/mechanism, a measurement finding, or an evidence regime nobody had covered? A faster implementation of a known scheme is not, by itself, an INFOCOM contribution. - **Cover the networking lanes.** INFOCOM reviewers expect the flagships and the journals, not just the papers nearest your method (see the table). A bibliography missing the obvious sibling work reads as unaware in a crowded pool. - **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 double-blind.** Cite your own prior work in the **third person** and never lin
- Positioning checks
- Networking literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the infocom-related-work skill do?
Use when positioning an IEEE INFOCOM submission against the networking literature across INFOCOM, SIGCOMM, NSDI, MobiCom, ICNP, and the journals (IEEE/ACM ToN, IEEE JSAC/TMC), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind on EDAS, and handling concurrent, preprint, and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.