sigcomm-submission
Use when running the final pre-upload audit of an ACM SIGCOMM submission — the abstract-registration-then-paper sequence on the SIGCOMM HotCRP site, the AoE deadline clock, the 12 single-spaced pre-reference pages including figures and tables, double-blind anonymization, ACM acmart formatting, and the research-versus-experience track choice.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-submission --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 Submission SIGCOMM gives you one main-track deadline a year, so this audit is unforgiving by design. Reopen the current CFP, submission page, and the HotCRP `/deadlines` clock before trusting any number below; the 2026 figures are a dated snapshot. ## Register the abstract, then upload the paper SIGCOMM 2026 opened abstract registration on **January 30, 2026** and full-paper upload on **
What does the sigcomm-submission skill do?
Use when running the final pre-upload audit of an ACM SIGCOMM submission — the abstract-registration-then-paper sequence on the SIGCOMM HotCRP site, the AoE deadline clock, the 12 single-spaced pre-reference pages including figures and tables, double-blind anonymization, ACM acmart formatting, and the research-versus-experience track choice.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-submission --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.