infocom-reproducibility
Use when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE reproducibility-badge options, and consistency between what the paper claims and what a reader could rebuild.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.
# INFOCOM Reproducibility Use this before submission and again before camera-ready. INFOCOM has **no formal artifact-evaluation track** (as of 2026-07-09; 待核实 whether a cycle adds one), so reproducibility is a matter of **credibility, not a badge you are forced to earn**. The goal is that a competent networking reader could rebuild your evidence and reach your conclusions from the paper plus any material you choose to release — which, at a large venue with no rebuttal, is how you convert a skeptical reviewer. ## Evidence map - Map each theorem, algorithm, and reported number to a **verifiable location** — a proof (in the body or a tight in-budget appendix), a simulator configuration, or a released script/dataset. - For analytical results, give enough of the assumptions, derivation, and parameters that a reader could re-derive or check the bound. A theorem whose proof is "omitted for space" with no pointer is a weakness a reviewer cannot rebut for you. - For simulation/measurement, report the simulator and version, topology and traffic model, seeds, number of runs, and the parameters — enough to re-run. - **Releasing code/data is optional but persuasive.** Where you can, deposit the
- Evidence map
- What "reproducible" means without a badge track
- Provenance and setup pinning
- IEEE reproducibility options (optional, post-decision)
- Degrees of reproducibility (state the one you achieved)
- Consistency and camera-ready pass
- Output format
What does the infocom-reproducibility skill do?
Use when strengthening IEEE INFOCOM reproducibility even though the venue runs no formal artifact-evaluation track, covering pinned simulator setups, released code and datasets where possible, complete proofs and parameters within the page budget, IEEE reproducibility-badge options, and consistency between what the paper claims and what a reader could rebuild.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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 984 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.