mobicom-related-work
Use when building or auditing the related-work of a MobiCom paper — sweeping the SIGMOBILE and networking literature lanes, proving each citation's venue on dblp/ACM DL against the INFOCOM/SIGCOMM/NSDI misattribution traps, positioning against the current rolling-cohort cohort, and self-citing without breaking double-blind.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.
# MobiCom Related Work Related work at MobiCom does two jobs: it proves you know the wireless/mobile-networking literature, and it draws the exact line between your mechanism and the nearest prior one. Because the field's canon is spread across ACM and IEEE venues, half the work is getting the *venue attribution right* — the most-cited wireless papers are the most-misfiled. ## The literature lanes to sweep Do not sweep "wireless" as one blob. Cover the lanes that a MobiCom reviewer occupies: - **MobiCom's own recent editions** — the two most recent programs, including the rolling cohort your round competes with; positioning against year-old work reads as stale. - **Sibling SIGMOBILE venues** — MobiSys, SenSys, IMWUT/UbiComp, HotMobile — where an adjacent mechanism may already live. - **Broad networking** — SIGCOMM, NSDI, INFOCOM — for the protocol/measurement lineage. - **PHY/communications** — where a coding or modulation primitive you build on originates. - **The specific mechanism's line** — the direct ancestors of your technique, traced to their origin paper, not a recent paper that cites it. ## Prove the venue before you cite A conference name in a slide deck or a re-hosted PD
- The literature lanes to sweep
- Prove the venue before you cite
- Position, do not enumerate
- Self-citation under double-blind
- Audit checklist
- Output format
Sanity-check a citation's venue and year against dblp (read via renderings if 403) dblp.org/db/conf/mobicom/ -> confirm edition number matches the claimed year For each load-bearing cite, record: authors | title | venue | year | pages
What does the mobicom-related-work skill do?
Use when building or auditing the related-work of a MobiCom paper — sweeping the SIGMOBILE and networking literature lanes, proving each citation's venue on dblp/ACM DL against the INFOCOM/SIGCOMM/NSDI misattribution traps, positioning against the current rolling-cohort cohort, and self-citing without breaking double-blind.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mobicom-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.