infocom-writing-style
Use when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-writing-style --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 Writing Style Use this when revising the main paper. INFOCOM papers are read by a **broad networking TPC** that spans theory and systems, inside a **nine-page IEEEtran budget** and (traditionally) with **no rebuttal**. Two constraints follow: the paper must be legible to both an analyst and a systems reader, and it must **pre-empt the reviewer's objection in the text**, because you will not get to answer it later. ## Revision rules - **State the networking problem and the system model first.** By the end of the introduction a reader should know the setting (topology, traffic, constraints), the gap, the contribution (analysis and/or design), and what improves. Do not open with a technology-trend paragraph. - **Make the model do work.** If you formulate an optimization or a Markov/queueing model, its assumptions must be stated plainly and its results must yield insight or an algorithm — not a formalism that the evaluation ignores. Reviewers reward a model whose theorem changes what you build or bound. - **Pair every claim with proportional evidence** — a proof for an analytical claim, a simulation/testbed number with the setup named, or a measurement with its methodology —
- Revision rules
- Networking-paper skeleton
- Sentence-level rewrites
- Defensive-writing discipline (no rebuttal)
- Vignette: compressing an over-scoped analytical paper
- Output format
What does the infocom-writing-style skill do?
Use when revising an IEEE INFOCOM paper for a networking problem and system model stated up front, theorems or protocol design that pay off, evaluation proportional to the claim, defensive writing that pre-empts objections (because there is no rebuttal), double-blind wording, and disciplined use of the tight IEEEtran two-column page budget.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-writing-style --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.