infocom-supplementary
Use when deciding what fits inside an IEEE INFOCOM paper's tight IEEEtran budget, covering the rule that appendices count toward the nine pages of text, the absence of a separate supplementary channel at review time, double-blind handling of any released material, and how to split an analytical or systems networking paper between the body and an optional external release.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-supplementary --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 Supplementary Use this when assembling INFOCOM material. The governing fact is blunt: **there is no separate supplementary or appendix upload at review time, and in-paper appendices count toward the nine pages of text.** The paper must be **complete and judgeable from the ten-page PDF alone.** Anything you want a reviewer to weigh must fit inside the budget; anything you release externally is optional context they may not open. ## What goes where | Content | Body (within the 9-page text budget) | Optional external release | |---|---|---| | Problem, system model, assumptions | Yes | — | | Main theorems and their proof (sketch in body, full proof in in-budget appendix) | Yes | The long-form technical report, if any | | Protocol/algorithm description | Yes | Reference implementation | | Headline results and honest baselines | Yes | Full result tables, extra plots | | Simulator configuration behind a claim | Named in the body | The scripts and configs | | Trace/dataset | Source + selection criteria | The dataset itself (if releasable) | | Reproduction instructions | A pointer (if you release) | The README and run scripts | If a reviewer would need to open an external file to
- What goes where
- The page-budget discipline (appendices included)
- Double-blind rules for any released material
- In-budget appendix architecture
- Vignette: splitting an analytical + simulation paper
- Output format
What does the infocom-supplementary skill do?
Use when deciding what fits inside an IEEE INFOCOM paper's tight IEEEtran budget, covering the rule that appendices count toward the nine pages of text, the absence of a separate supplementary channel at review time, double-blind handling of any released material, and how to split an analytical or systems networking paper between the body and an optional external release.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-supplementary --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.