sosp-author-response
Use when drafting a SOSP author response during the pre-PC-meeting rebuttal window, keeping it within the venue's norms — correcting factual errors, answering direct reviewer questions, staying near the 500-word guidance, and never introducing new experiments, new data, or promises of future work.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-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.
# SOSP Author Response Use this when SOSP reviews land and the response window opens. SOSP's response phase has an unusually narrow charter, stated in the CFP (verified 2026-07-08 for the 2026 cycle): responses exist to **correct factual errors in the reviews** and to **answer questions reviewers explicitly posed**. They must not add new experiments or data, describe work done since submission, or promise follow-up work. Submitting a response is optional, and while no hard cap is stated, authors are strongly encouraged to stay **under 500 words**. ## What the response can and cannot do The response is read by a program committee that will discuss the paper live at a PC meeting. Its job is to remove false obstacles before that discussion, not to renegotiate the paper. | Move | Allowed at SOSP? | Why | |---|---|---| | "Review B states we hold the lock across I/O; §4.2 shows it is released before the write" | Yes | Factual correction, cites the submitted text | | Answering "how does this behave when the log fills?" with what the submission already supports | Yes | Direct reviewer question | | "We have since run the benchmark on 128 nodes and..." | No | New data after the deadline | |
- What the response can and cannot do
- Hour-zero triage
- Budgeting 500 words
- Tone calibration for a single-track PC
- Common failure modes
- Output format
What does the sosp-author-response skill do?
Use when drafting a SOSP author response during the pre-PC-meeting rebuttal window, keeping it within the venue's norms — correcting factual errors, answering direct reviewer questions, staying near the 500-word guidance, and never introducing new experiments, new data, or promises of future work.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sosp-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.