sigcomm-camera-ready
Use when preparing an accepted ACM SIGCOMM paper for the TAPS proceedings — clearing shepherd sign-off in HotCRP, uploading the final PDF plus source under acmart, de-anonymizing author and deployment identity, keeping the 12-page body under ACM two-column reflow, appendix-necessity approval, and releasing the public artifact by the badge deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-camera-ready --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 Camera Ready Use this after acceptance. Reopen the current camera-ready instructions, the ACM TAPS requirements, and your shepherd's HotCRP thread before finalizing; the 2026 cycle set the camera-ready deadline at **July 3, 2026, 23:59 UTC**, with the final version approved by the shepherd via a HotCRP comment. ## Clear the shepherd first At SIGCOMM the shepherd gates the final version. Before you polish anything: - Map each review and meta-review concern to a concrete edit and confirm the mapping with the shepherd through HotCRP comments — do not assume silence is approval. - The shepherd also **approves whether any appendix is necessary**; be ready to justify each appendix or fold it into the body, and expect to remove one that is not load-bearing. - Do not strengthen the accepted contribution into something reviewers never evaluated; camera-ready is clarification and integration, not a new result. ## De-anonymization sweep | Anonymized in submission | Restored for camera-ready | |---|---| | Author names, affiliations, ORCIDs | Full author block in ACM metadata and PDF | | Acknowledgments and funding | Restored, spelled out | | Deployment / system / company names | Real
- Clear the shepherd first
- De-anonymization sweep
- ACM two-column reflow
- The TAPS pipeline
- Release the artifact on its own clock
- Output format
What does the sigcomm-camera-ready skill do?
Use when preparing an accepted ACM SIGCOMM paper for the TAPS proceedings — clearing shepherd sign-off in HotCRP, uploading the final PDF plus source under acmart, de-anonymizing author and deployment identity, keeping the 12-page body under ACM two-column reflow, appendix-necessity approval, and releasing the public artifact by the badge deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-camera-ready --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.