Menu

Individual skill

infocom-reproducibility

0upvotes

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.

INFOCOM-Skills/skills/infocom-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,411
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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
Back to top