oopsla-supplementary
Use when deciding what rides along with an OOPSLA submission beyond the 23-page body — appendices, full proofs or mechanizations, extended tables, anonymized code — keeping the package double-anonymous, self-consistent with the PDF, and honest about what reviewers are obliged to read versus what a revision can absorb.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-supplementary --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 Supplementary Material The 23-page cap on an OOPSLA initial submission excludes references, required statements, and appendices — so "supplementary" at OOPSLA is less a separate upload category than a *layering decision*: what must live in the reviewed body, what sits in appendices the body can survive without, and what waits for the artifact stage after acceptance. The controlling rule set is the current call (待核实 per cycle for upload mechanics on HotCRP); the controlling *strategy* is the two-round review model. ## The layering rule A reviewer deciding among Accept, Minor Revision, Major Revision, and Reject must be able to reach a verdict **from the body alone**. Appendices exist to let a skeptical reviewer verify, not to let the body skip its argument. | Layer | Belongs there | Test | | --- | --- | --- | | Body (≤23 pp) | Claim statements, mechanism, proof sketches, headline evaluation, threats | Could a reviewer bucket the paper reading only this? | | Appendix / supplement | Full proofs, extra benchmarks, case-study transcripts, calculus metatheory details | Does the body *state* what the appendix *establishes*? | | Artifact (post-acceptance) | Runnable code, raw data
- The layering rule
- Anonymity applies to every byte
- Consistency: the silent killer across rounds
- What NOT to put in the supplement
- Revision-round dynamics
- Output format
What does the oopsla-supplementary skill do?
Use when deciding what rides along with an OOPSLA submission beyond the 23-page body — appendices, full proofs or mechanizations, extended tables, anonymized code — keeping the package double-anonymous, self-consistent with the PDF, and honest about what reviewers are obliged to read versus what a revision can absorb.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-supplementary --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.