soda-author-response
Use when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response deadline, triaging referee misreadings versus real gaps, and writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-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.
# SODA Author Response SODA runs a short rebuttal, and short is the operative word. For the 2027 cycle, initial reviews reach authors by **September 1, 2026** and responses are due **September 4, 2026** (checked 2026-07-08 via the SIAM SODA27 submission page, read through search rendering). SODA 2026's rebuttal phase opened September 8, 2025, in a record-submission year — the window is a house institution now, not an experiment, but its exact dates, length caps, and mechanics are reset per cycle (caps for 2027: 待核实 on the HotCRP response form when it opens). ## What three days buys — and what it cannot A SODA response is not a negotiation channel. It exists so the PC can distinguish "the referee missed Lemma 4.2" from "Lemma 4.2 is actually broken" before the October decision meeting. Budget accordingly: | Review problem | Response leverage | Play | |---|---|---| | Referee misread a definition or bound | High | Quote the exact line and page; one sentence of correction | | Referee missed a proof in the back matter | High | Point to the section; the full version was submitted, so it is on record | | "Improvement too incremental" | Low-medium | One paragraph: name the barrier the prio
- What three days buys — and what it cannot
- Preparation happens in August
- Writing discipline
- Response skeleton
- The 72-hour schedule that actually works
- After the response
- Output format
What does the soda-author-response skill do?
Use when drafting the SODA (ACM-SIAM Symposium on Discrete Algorithms) rebuttal — the roughly three-day window between review release in early September and the response deadline, triaging referee misreadings versus real gaps, and writing terse theorem-anchored replies inside HotCRP without breaking lightweight double-blind rules.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-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.