infocom-experiments
Use when designing or auditing IEEE INFOCOM evaluations, covering analytical results with stated and justified assumptions, simulation with a named simulator and logged seeds, testbed and measurement studies with real traffic, honest and tuned baselines, and matching evidence to the shape of each networking claim across the analysis-simulation-testbed spectrum.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-experiments --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 Experiments Use this before submission when the evaluation is not yet locked. INFOCOM reviewers span the full **analysis → simulation → testbed** spectrum, and the evaluation is where a good idea is won or lost — especially since there is (traditionally) **no rebuttal** to repair a weak comparison. The organizing principle is **evidence proportional to the claim**, delivered by the method the claim demands: a bound needs a proof, a design needs a fair experiment, a behavior claim needs measurement. ## Evaluation audit - **Match the method to the claim.** An *optimality/approximation* claim needs a **proof** under stated assumptions; a *performance* claim needs a **fair experiment**; a *real-world behavior* claim needs **measurement** on real traffic. A simulation cannot substitute for a proof, and a proof under unrealistic assumptions cannot substitute for an experiment. - **State and justify every assumption.** For analytical work, list the assumptions (A1, A2, ...) and defend each; a theorem true only under an assumption no network satisfies is a scored weakness a reviewer will name — and you cannot rebut it. - **Name the simulator and pin the setup.** State whether it
- Evaluation audit
- Claim-to-evidence design table
- Simulation and reproducibility floor
- Analytical-work floor
- Vignette: evaluating a caching/offloading policy
- Statistical reporting floor
- Output format
What does the infocom-experiments skill do?
Use when designing or auditing IEEE INFOCOM evaluations, covering analytical results with stated and justified assumptions, simulation with a named simulator and logged seeds, testbed and measurement studies with real traffic, honest and tuned baselines, and matching evidence to the shape of each networking claim across the analysis-simulation-testbed spectrum.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-experiments --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.