sigcomm-author-response
Use when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the discussion phase, and building the revision packet (point-by-point response, change-marked manuscript, and list of changes) against the required-changes contract.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-author-response --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 Author Response SIGCOMM has two distinct author-facing replies, and conflating them is a strategic error. The **rebuttal** is a short argument during the discussion phase; the **one-shot revision** is a month-long, shepherd-managed contract. Reopen the current CFP to confirm the mechanics before drafting. ## First, know which reply you are writing | Signal in the letter | You are in | Th
What does the sigcomm-author-response skill do?
Use when drafting an ACM SIGCOMM rebuttal or executing a shepherd-run one-shot revision — triaging reviewer issues, writing a decision-focused anonymous rebuttal for the discussion phase, and building the revision packet (point-by-point response, change-marked manuscript, and list of changes) against the required-changes contract.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigcomm-author-response --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.