infocom-artifact-evaluation
Use when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.
# INFOCOM Artifact Evaluation Use this when you want to release an artifact. The first thing to internalize: **INFOCOM has no standing artifact-evaluation track and no mandatory badge process** (as of 2026-07-09; 待核实 whether a cycle introduces one). Unlike SIGCOMM/NSDI/USENIX ATC — where a separate committee runs your artifact and awards badges — an INFOCOM artifact is **entirely optional and self-directed**. That changes the goal: you package not to pass an evaluator, but to make a large, skeptical, no-rebuttal reviewer pool believe your numbers. ## What the absence of a formal track changes | At an artifact-track venue (SIGCOMM/NSDI/ATC) | At INFOCOM | |---|---| | A committee runs your artifact on a deadline | No one is required to run it | | Badges (Available/Functional/Reproduced) are awarded | No INFOCOM badge exists (待核实 per cycle) | | Packaging is a graded deliverable | Packaging is a credibility investment you choose | | The artifact can lift a borderline decision | A released package pre-empts "I don't believe this" in the PDF | Because no evaluator is guaranteed, the payoff of a release is **reviewer trust and post-publication impact**, not a badge. Optimize for a reader
- What the absence of a formal track changes
- IEEE reproducibility options you can opt into
- What a credible networking release contains
- Packaging plan (optional but persuasive)
- Double-blind timing
- Vignette: releasing a scheduling simulator + trace
- Calibration
- Output format
What does the infocom-artifact-evaluation skill do?
Use when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-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.