Menu

Individual skill

infocom-writing-style

0upvotes

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.

INFOCOM-Skills/skills/infocom-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,410
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top