CoNEXT Skills

A 12-skill depth pack for ACM CoNEXT (International Conference on emerging Networking EXperiments and Technologies), whose research papers publish in PACMNET (Proceedings of the ACM on Networking): its two annual submission cycles (December and June) feeding one program, the journal-style one-shot 'major' revision decision, double-anonymous HotCRP submission, the SIGCOMM public-review and shepherd

by @brycewang-stanford 12 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/conext-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-conext-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

▌
Conext Workflow · brycewang-stanford
Use when planning an ACM CoNEXT campaign backward from a deadline, covering the choice between the December and June submission cycles, the mandatory registration step, the one-shot major-revision window, the reproducibility badge opt-in due at submission, PACMNET camera-ready, and presentation — all on CoNEXT's distinctive two-cycles-per-year calendar.

1k repo stars
▌
Conext Submission · brycewang-stanford
Use when auditing an ACM CoNEXT submission for HotCRP readiness, covering the choice between the December and June cycles, the mandatory paper-registration step, the ACM acmart page budget (long ≤16 + ≤4 appendix; short ≤10 + ≤2 appendix), double-anonymous review, the reproducibility badge opt-in due at submission, PACMNET publication, and desk-reject triage before the cutoff.

1k repo stars
▌
Conext Experiments · brycewang-stanford
Use when designing or auditing the evaluation of an ACM CoNEXT paper — matching evidence to claim shape with real testbeds and deployments, honest and tuned baselines, measurement statistics and uncertainty, trace and config provenance, and contamination-aware ablations for ML-for-networking work.

1k repo stars
▌
Conext Camera Ready · brycewang-stanford
Use when preparing the camera-ready of an accepted ACM CoNEXT paper for its assigned PACMNET issue — systematically de-anonymizing, completing PACMNET journal metadata and ACM rights/CCS/keywords, permanentizing artifact and DOI links, applying any shepherd-required changes, and passing ACM production checks.

1k repo stars
▌
Conext Related Work · brycewang-stanford
Use when writing the related-work and positioning of an ACM CoNEXT paper — covering the networking literature lanes (SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, CCR), delta-first positioning against the venue's own recent programs, and keeping self-citations double-anonymous.

1k repo stars
▌
Conext Supplementary · brycewang-stanford
Use when deciding what goes in the ACM CoNEXT main body versus the appendix budget versus the artifact — splitting content by decision-criticality so nothing a reviewer needs to accept the paper hides in an appendix or repository, within the acmart limits (long ≤4 appendix pages, short ≤2).

1k repo stars
▌
Conext Writing Style · brycewang-stanford
Use when shaping the prose and structure of an ACM CoNEXT paper — leading with the networking problem and deployment context, tying every claim to a measurement on the real target platform, arguing limitations rather than reciting them, and holding the acmart page budget for long (≤16) and short (≤10) papers.

1k repo stars
▌
Conext Review Process · brycewang-stanford
Use when reasoning about how an ACM CoNEXT submission is evaluated, covering double-anonymous review, the two-round TPC process with online discussion and a TPC meeting, the Accept / Reject / one-shot "major" revision decision categories, the journal-style revise-and-resubmit re-read by the original reviewers, shepherding, and how CoNEXT's two-cycle process differs from SIGCOMM and NSDI.

1k repo stars
▌
Conext Author Response · brycewang-stanford
Use when drafting ACM CoNEXT author responses, covering the initial-review rebuttal and — distinctively — the one-shot "major" revision response letter that must stay double-anonymous, map every "minimum necessary change" to a concrete tracked edit, and survive a single re-review by the original reviewers and a shepherd under PACMNET.

1k repo stars
▌
Conext Reproducibility · brycewang-stanford
Use when building the reproducibility story for an ACM CoNEXT paper — pinned traces and configs, a runnable artifact, an honest data-availability posture, and the one-page artifact description the CoNEXT reproducibility committee needs — remembering that the ACM badge opt-in is due before the submission deadline.

1k repo stars
▌
Conext Topic Selection · brycewang-stanford
Use when deciding whether a networking project belongs at ACM CoNEXT or should be routed to SIGCOMM, NSDI, IMC, SIGMETRICS, MobiCom, or HotNets, and when using CoNEXT's two-cycles-per-year calendar and PACMNET journal-style fit to choose the venue and the cycle by contribution shape and evidence maturity.

1k repo stars
▌
Conext Artifact Evaluation · brycewang-stanford
Use when converting an accepted ACM CoNEXT paper's package into optional ACM reproducibility badges via the CoNEXT reproducibility committee — from the badge opt-in due before submission, to the one-page artifact description due within a week of acceptance, to the Available / Functional / Reusable / Reproduced criteria and evaluator-proof reuse docs.

1k repo stars