sigcomm-supplementary
Use when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper self-contained, anticipating the shepherd's appendix-necessity approval, and placing extended measurements and proofs outside the cap without hiding load-bearing content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-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.
# SIGCOMM Supplementary Use this when splitting a SIGCOMM paper across body, references, and appendices. The controlling rule: the 12 single-spaced pages before references must carry the argument on their own; appendices and references sit outside the cap but do not rescue an incomplete body. Reopen the current CFP to confirm this edition's appendix handling. ## What goes where - **Body (≤ 12 sing
What does the sigcomm-supplementary skill do?
Use when organizing the material around an ACM SIGCOMM paper — deciding what lives in the 12-page body versus references versus optional appendices, keeping the main paper self-contained, anticipating the shepherd's appendix-necessity approval, and placing extended measurements and proofs outside the cap without hiding load-bearing content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-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.