conext-reproducibility
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-reproducibility --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.
# CoNEXT Reproducibility Build the reproducible-networking story alongside the experiments, not after acceptance. CoNEXT runs a dedicated **reproducibility committee** that awards **optional ACM badges**, and the single most missed rule is that **badge eligibility requires opting in before the paper submission deadline** — you cannot bolt it on later. Even for authors who skip badging, a reproducible artifact strengthens a double-anonymous, one-shot-revision review. ## The timing trap (read this first) ```text [Before the submission deadline] OPT IN for ACM badging (required for eligibility) [At submission] anonymized, runnable artifact referenced from the paper [Within ~1 week of acceptance] send a ONE-PAGE artifact description to the reproducibility committee with pointers to code and other artifacts [Camera-ready / post-accept] committee evaluates for Available / Functional / Reusable / Reproduced badges (see conext-artifact-evaluation) ``` Miss the opt-in and the strongest artifact in the world cannot earn a badge this cycle. ## What "reproducible" means for a networking paper Networking reproducibility is harder than "here is the code," because the result depends on an environ
- The timing trap (read this first)
- What "reproducible" means for a networking paper
- Pin provenance at collection time
- Honest data-availability posture
- Anonymity of the artifact (double-anonymous review)
- The one-page artifact description
- Pre-submission reproducibility audit
- Output format
What does the conext-reproducibility skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill conext-reproducibility --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.