pods-author-response
Use when drafting ACM PODS author responses, covering the short ~48-hour double-anonymous rebuttal that corrects misreadings of proofs and definitions, and — distinctively — the shepherded revision cover letter that maps every required item to a concrete change in the resubmitted paper and survives the shepherd's second read.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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.
# PODS Author Response Use this after PODS reviews are released. PODS has **two distinct speaking turns**, and conflating them is a common mistake: a short **rebuttal** (about 48 hours, a few thousand characters) right after reviews, and — if you receive a **revision** decision — a **revision cover letter** accompanying a resubmitted paper that a **shepherd** re-reads. Both stay double-anonymous: do not reveal authors, affiliations, or a named system, even to strengthen a point. ## Triage (both turns) - Answer what affects correctness first: a claimed error in a proof, an unstated assumption, a mismatch between an upper and a lower bound, or an out-of-scope objection. - Distinguish a **misreading** (the reviewer misunderstood a definition or missed an existing appendix proof — fixable now, in the rebuttal) from a **real gap** (a step that genuinely needs to be written — fixable only in the revision). - Keep every word anonymous: no institution, no funder, no real system name, no "our earlier work" phrased in the first person. ## Turn 1 — the 48-hour rebuttal Short and correctness-focused. The rebuttal exists to **clarify misunderstandings and factual errors via pointers to the subm
- Triage (both turns)
- Turn 1 — the 48-hour rebuttal
- Turn 2 — the revision cover letter (the distinctive PODS move)
- Reviewer pushback patterns
- Anonymity in the response (easy to slip)
- Calibration
- Output format
What does the pods-author-response skill do?
Use when drafting ACM PODS author responses, covering the short ~48-hour double-anonymous rebuttal that corrects misreadings of proofs and definitions, and — distinctively — the shepherded revision cover letter that maps every required item to a concrete change in the resubmitted paper and survives the shepherd's second read.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill pods-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 984 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.