infocom-topic-selection
Use when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC), distinguishing INFOCOM by its breadth, its analytical/optimization tradition alongside systems, and the modeling-vs-building axis.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-topic-selection --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 Topic Selection Decide the venue before drafting. INFOCOM — the IEEE International Conference on Computer Communications, the IEEE ComSoc networking flagship — is the **broad, large-scale** networking venue. Its defining feature relative to its siblings is **breadth plus a living analytical tradition**: a well-posed model with a theorem and a convincing evaluation is a first-class INFOCOM paper, not a second-class one. A pure systems-building paper is welcome, but so is a scheduling/optimization/queueing/game-theory result that SIGCOMM or NSDI would push to a journal. ## The routing question that matters most The decisive question is rarely "is this networking?" but **"is the contribution a model/analysis, a built system, or a measurement — and which community rewards that shape now?"** INFOCOM is the safe home for the analytical and the broad; SIGCOMM/NSDI pull toward built-and-measured systems with a deployment story. Use the finer signals below and the live calendar to choose. ## Sibling-venue routing table | Signal in your project | Better home | Why | |---|---|---| | Modeling/optimization/algorithmic core (scheduling, resource allocation, queueing, game theory, netwo
- The routing question that matters most
- Sibling-venue routing table
- Contribution shapes INFOCOM rewards
- The modeling-vs-building and model-swap tests
- Evidence maturity, without the ladder cliché
- Cheap reconnaissance before committing
- Decision procedure
What does the infocom-topic-selection skill do?
Use when deciding whether a networking project belongs at IEEE INFOCOM or should be routed to SIGCOMM, NSDI, MobiCom, ICNP, or an IEEE/ACM networking journal (ToN, JSAC), distinguishing INFOCOM by its breadth, its analytical/optimization tradition alongside systems, and the modeling-vs-building axis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-topic-selection --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.