sigcomm-workflow
Use when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the early-reject/rebuttal/one-shot-revision review pipeline, shepherd-run camera-ready, TAPS proceedings, artifact evaluation, and forward planning for the next edition.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow --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 Workflow Use this as the project-management skill for a SIGCOMM campaign. The defining constraint is one main-track deadline per year feeding one August conference: there is no fall gate, so the plan is a year-long backward schedule from February, not a two-shot hedge. Replace every date with the current official timetable. SIGCOMM is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. The rotating leadership is the per-edition General Chairs and Program Committee Co-Chairs (the 2026 roster was not retrievable on 2026-07-09 — 待核实), and the cost model is registration, not APCs; proceedings publish through ACM TAPS into the ACM Digital Library. Chairs rotate yearly, so re-check the current organization page. ## Milestones - **Venue fit and track**: confirm a networking-stack mechanism and pick research vs. experience. - **Evidence lock**: freeze the testbed, traces, workloads, baselines, measurement methodology, and the tail metrics before writing hardens. - **Abstract registration**: real title, authors, topics, conflicts on HotCRP. - **Full-paper upload**: anonymous PDF, 12 single-spaced pre-reference pages, ACM template. - **
- Milestones
- Backward plan from the February paper deadline
- The year has two halves, not one deadline
- Failure modes by stage
- Coordination notes
- Output format
What does the sigcomm-workflow skill do?
Use when planning an ACM SIGCOMM project timeline around the single yearly deadline — venue fit, evidence lock, abstract registration and paper upload in February, the early-reject/rebuttal/one-shot-revision review pipeline, shepherd-run camera-ready, TAPS proceedings, artifact evaluation, and forward planning for the next edition.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-workflow --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.