SIGCOMM Skills

A 12-skill depth pack for ACM SIGCOMM submissions: the single-February-deadline flagship venue fit, HotCRP double-blind submission audits, the rebuttal + shepherd-run one-shot revision, deployment- and measurement-grade evaluation, ACM artifact badges and reproducible 'runnable papers', and TAPS camera-ready proceedings. Grounded in the ACM SIGCOMM 2026 CFP, submission and camera-ready pages, and

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/sigcomm-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 12 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-sigcomm-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 12
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Sigcomm Workflow · brycewang-stanford
Use when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the early-reject/rebuttal/one-shot-revision review pipeline, shepherd-run camera-ready, TAPS proceedings, artifact evaluation, and forward planning for the next edition.

1k repo stars
▌
Sigcomm Submission · brycewang-stanford
Use when running the final pre-upload audit of an ACM SIGCOMM submission — the abstract-registration-then-paper sequence on the SIGCOMM HotCRP site, the AoE deadline clock, the 12 single-spaced pre-reference pages including figures and tables, double-blind anonymization, ACM acmart formatting, and the research-versus-experience track choice.

1k repo stars
▌
Sigcomm Experiments · brycewang-stanford
Use when designing or auditing ACM SIGCOMM experiments — climbing the evidence ladder from microbenchmarks to testbed and trace replay to deployment, choosing baselines that match the deployed state of the art, reporting tail percentiles and variance over repeated trials, mapping break points, and holding the fair variable fixed.

1k repo stars
▌
Sigcomm Camera Ready · brycewang-stanford
Use when preparing an accepted ACM SIGCOMM paper for the TAPS proceedings — clearing shepherd sign-off in HotCRP, uploading the final PDF plus source under acmart, de-anonymizing author and deployment identity, keeping the 12-page body under ACM two-column reflow, appendix-necessity approval, and releasing the public artifact by the badge deadline.

1k repo stars
▌
Sigcomm Related Work · brycewang-stanford
Use when positioning an ACM SIGCOMM submission against the networking literature — sweeping SIGCOMM, NSDI, MobiCom, CoNEXT, IMC, and SIGMETRICS plus journals, proving each placement via dblp and the ACM Digital Library, distinguishing main-track papers from CCR editorials, handling concurrent work, and keeping self-citation double-blind-safe.

1k repo stars
▌
Sigcomm Supplementary · brycewang-stanford
Use when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper self-contained, anticipating the shepherd's appendix-necessity approval, and placing extended measurements and proofs outside the cap without hiding load-bearing content.

1k repo stars
▌
Sigcomm Writing Style · brycewang-stanford
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.

1k repo stars
▌
Sigcomm Review Process · brycewang-stanford
Use when explaining or planning around ACM SIGCOMM peer review — double-blind HotCRP reviewing, the early-reject cut for consensus rejections, the rebuttal for discussion-phase papers, the shepherd-run one-shot revision that ends in accept or reject only, shepherding of accepted papers, and how the outcome space shapes author strategy.

1k repo stars
▌
Sigcomm Author Response · brycewang-stanford
Use when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the discussion phase, and building the revision packet (point-by-point response, change-marked manuscript, and list of changes) against the required-changes contract.

1k repo stars
▌
Sigcomm Reproducibility · brycewang-stanford
Use when strengthening the reproducibility evidence of an ACM SIGCOMM paper — topology and testbed ledgers, traffic workload and trace provenance, configuration and version pinning, tail-percentile run counts and variance, legal data-release decisions, and consistency between the paper's claims and the artifact that backs them.

1k repo stars
▌
Sigcomm Topic Selection · brycewang-stanford
Use when deciding whether a project is a strong ACM SIGCOMM fit, choosing the research versus experience track, identifying the networking-stack mechanism at the core of the contribution, and routing misfits to NSDI, MobiCom, CoNEXT, IMC, SIGMETRICS, or a systems venue before writing begins.

1k repo stars
▌
Sigcomm Artifact Evaluation · brycewang-stanford
Use when packaging an ACM SIGCOMM paper's code, traces, topologies, and configuration for the artifact-evaluation committee — choosing ACM badges (Artifacts Available, Evaluated, Results Reproduced) as claim calibration, building downscaled topologies and trace substitutes, and making a networking testbed result rebuildable by a reviewer.

1k repo stars