oopsla-author-response
Use when writing an OOPSLA author response inside the short per-round window — reading reviews through the four-outcome lens (Accept, Minor Revision, Major Revision, Reject), steering borderline papers toward a revision outcome instead of rejection, and committing only to changes deliverable within the round's revision mechanics.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-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.
# OOPSLA Author Response Each OOPSLA round gives authors one written response before decisions are finalized; the 2026 call scheduled it as a four-day Tuesday-to-Friday window per round (exact 2026 dates 待核实 — read them off the live HotCRP instance). What makes the OOPSLA response unlike a classic rebuttal is the decision space: reviewers are not only choosing accept-or-reject, they are choosing among **Accept, Minor Revision, Major Revision, and Reject** (2026 merged the old Conditional Accept into Minor Revision). Your response is an argument about *which bucket the paper's problems belong in*. ## Reframe every objection as a bucket question | Reviewer concern type | Bucket you argue for | Argument shape | | --- | --- | --- | | Factual misreading | Accept | Quote the submitted PDF: section, page, exact sentence | | Missing experiment, bounded scope | Minor Revision | Show the experiment is runnable in weeks; sketch the protocol | | Evaluation redesign, new formalism | Major Revision (next round) | Concede scale honestly; state what the revision would contain | | "Wrong venue" / fit doubts | Accept or MR | Anchor to precedent shapes (see `resources/exemplars/library.md`) | | Sound
- Reframe every objection as a bucket question
- Composition rules
- Triage worksheet
- If the outcome will be a revision anyway
- Output format
What does the oopsla-author-response skill do?
Use when writing an OOPSLA author response inside the short per-round window — reading reviews through the four-outcome lens (Accept, Minor Revision, Major Revision, Reject), steering borderline papers toward a revision outcome instead of rejection, and committing only to changes deliverable within the round's revision mechanics.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-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.