oopsla-writing-style
Use when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics, journal-article pacing inside the 23-page cap, and honest threats-to-validity prose that preempts the revision lever rather than triggering it.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-writing-style --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 Writing Style An OOPSLA paper is read twice by design: once by a committee choosing among four outcomes, and again — possibly by the same people — if a revision comes back. Style at this venue therefore optimizes for *checkability*: a paper whose claims can be verified paragraph by paragraph collects bounded revision demands (or none), while a paper that argues by adjective collects unbounded ones. The published form is a journal article (PACMPL), and the prose should carry that register: measured, self-contained, built to be cited. ## Voice calibration | Draft habit | OOPSLA replacement | | --- | --- | | "We present NovelTool, a novel system for..." | Name the design question and your answer; the tool arrives as evidence (see `resources/worked-examples/01-introduction.md`) | | "Our approach significantly outperforms..." | The number, the baseline, the workload, the dispersion — or nothing | | "To the best of our knowledge, first..." | A positioning sentence naming the nearest prior work and the delta (`oopsla-related-work`) | | "Due to space limitations, details are in the appendix" | A body-level statement of what the appendix establishes (`oopsla-supplementary`) | | A w
- Voice calibration
- The running example as load-bearing structure
- Claims that survive two readings
- Journal pacing inside 23 pages
- Revision-aware editing
- Output format
What does the oopsla-writing-style skill do?
Use when revising a draft into OOPSLA's register — design insight stated before the artifact, claims written to be falsifiable, motivating examples that carry semantics, journal-article pacing inside the 23-page cap, and honest threats-to-validity prose that preempts the revision lever rather than triggering it.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-writing-style --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.