socc-author-response
Use when drafting an ACM SoCC author response (rebuttal) during a round's response window, covering the single written turn, answering both the systems and the data/measurement reviewer, supplying the tail-latency and cost numbers reviewers ask for, staying within dual anonymity, and the fact that SoCC has no Major-Revision round to fall back on.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.
# SoCC Author Response Use this after SoCC reviews are released, during the round's **author-response (rebuttal) window** (SoCC 2026 Round 2: 10-12 Sep 2026). SoCC gives you **one written turn**, not a journal-style revise-and-resubmit — there is no Major Revision to repair the paper in, so the rebuttal must do all the persuading before the PC discussion decides. Because the reviewer pool is drawn from **both SIGMOD and SIGOPS**, a winning rebuttal answers the *systems* reviewer and the *data/measurement* reviewer, not one at the expense of the other. ## Triage - Answer what affects the decision: significance of the cloud contribution, soundness of the mechanism, realism of the deployment or trace, and the measurement quality — especially **tail latency and cost**, the numbers reviewers most often say are missing. - Prioritize by impact-times-fixability: a factual misreading you can correct, or a number you can supply from existing logs, moves more than a philosophical disagreement. - Correct factual misreadings first; a reviewer who misread a table or a workload is often persuadable. - Keep every word within dual anonymity: do not reveal your cluster, company, provider, trace prov
- Triage
- Structure the single turn
- Reviewer pushback patterns
- What a SoCC rebuttal may and may not do
- Anonymity in the rebuttal (easy to slip)
- Calibration
- Output format
What does the socc-author-response skill do?
Use when drafting an ACM SoCC author response (rebuttal) during a round's response window, covering the single written turn, answering both the systems and the data/measurement reviewer, supplying the tail-latency and cost numbers reviewers ask for, staying within dual anonymity, and the fact that SoCC has no Major-Revision round to fall back on.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-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.