sigcomm-artifact-evaluation
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-artifact-evaluation --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.
# SIGCOMM Artifact Evaluation Use this for the post-acceptance artifact submission. SIGCOMM helped establish artifact evaluation in networking, and the venue's "runnable papers" culture sets a high bar: a committee attempts to build and, where a badge requires it, reproduce your headline result. Reopen the current Call for Artifacts for this edition's exact badge set and dates (待核实 for 2026). ## B
What does the sigcomm-artifact-evaluation skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-artifact-evaluation --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.