Individual skill

sigcomm-writing-style

Use when revising an ACM SIGCOMM paper for its house style — leading with measured operational pain, stating a design principle rather than a behavior, pairing every claim with testbed/trace/deployment evidence, reporting tails instead of superlatives, and fitting the argument into 12 figure-inclusive pages while keeping blinding clean.

SIGCOMM-Skills/skills/sigcomm-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Network or broad shell
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,405
Repository last updated: Sep 27, 2026
License: MIT

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

academic-writing Repository topic
agent-skills Repository topic
journal Repository topic
academic-research Repository topic
ai-agents Repository topic
anthropic Repository topic
awesome-list Repository topic
claude Repository topic
claude-code Repository topic
economics Repository topic
design Derived category
writing Derived category
devops Derived category
research Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 4,148 bytes

Read excerpt


# SIGCOMM Writing Style

Use this when revising the main paper. A SIGCOMM paper has to make a networking mechanism feel
inevitable: the reader should see the measured problem, the principle that solves it, and the
evidence that it works under real conditions — inside 12 pages where figures count. Reopen the
current CFP for format specifics.

## Revision rules

- **Lead with measured pain.** Put the operational cost in numbers on the first page — which
  percentile, how bad, under what traffic — not "congestion is a well-known problem." An
  asserted motivation is the first thing a SIGCOMM reviewer discounts.
- **Name the design principle.** State the invariant your mechanism defends, not just what it
  does. "Steer at the timescale congestion forms" is a principle; "avoids hotspots" is a