ppopp-author-response
Use when writing a PPoPP author-response rebuttal, covering the short fixed word-capped window, answering the recurring "does it scale?" and "what about baseline X?" questions with pre-run numbers, correcting factual misreadings of a concurrency argument, staying double-blind, and prioritizing the points that can actually move a decision.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-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.
# PPoPP Author Response Write the rebuttal for the fixed **author-response window** (PPoPP 2026: 27–29 October 2025). This is a **short, word-capped, single written turn** — as verified there is no guaranteed revise-and-resubmit round to fall back on. Reviewers read it, discuss, and decide. Spend the budget on the points that can change a verdict, answered with data, not adjectives. ## What the window is and is not - It is a **2–3 day** window with a **word cap**; you cannot run a month of new experiments. - It is **not** a debate forum or a place to relitigate taste. It is where you correct factual misreadings and supply the specific number a reviewer said was missing. - It stays **double-blind**: reveal no identity, name no cluster/grant, add no author-revealing link. ## Triage the reviews first ```text [Blocking + fixable] a missing baseline you pre-ran; a scaling point you already have; a misread correctness argument -> answer these first, with data [Blocking + not fixable in words] a study-design gap needing new machine time -> concede honestly, scope the claim down, or note it as future work [Non-blocking] wording, a citation, a minor clarification -> one line each, or skip `
- What the window is and is not
- Triage the reviews first
- The two questions you must be ready for
- Answering a misread correctness argument
- Writing mechanics
- What not to do
- Output format
What does the ppopp-author-response skill do?
Use when writing a PPoPP author-response rebuttal, covering the short fixed word-capped window, answering the recurring "does it scale?" and "what about baseline X?" questions with pre-run numbers, correcting factual misreadings of a concurrency argument, staying double-blind, and prioritizing the points that can actually move a decision.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ppopp-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.