OOPSLA Skills

A 12-skill depth pack for OOPSLA papers published as PACMPL Issue OOPSLA: choosing a submission round, the two-round Accept/Minor-Revision/Major-Revision/Reject pipeline, revision strategy, artifact badges, SIGPLAN empirical standards, and SPLASH presentation. Grounded in the OOPSLA 2026 CFP and PACMPL sources checked on 2026-07-08.

by @brycewang-stanford 11 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/oopsla-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 11 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-oopsla-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 11
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Oopsla Workflow · brycewang-stanford
Use when planning an OOPSLA campaign on the two-round clock — choosing October vs March entry, budgeting for Minor or Major Revision paths, mapping acceptance to the OOPSLA1 or OOPSLA2 PACMPL issue, scheduling artifact evaluation, and landing the SPLASH talk, with dates re-anchored to the live cycle.

1k repo stars
▌
Oopsla Submission · brycewang-stanford
Use when preparing or auditing an OOPSLA submission — picking between the two yearly PACMPL rounds, meeting the 23-page acmsmall anonymous format, writing the required Data-Availability Statement, clearing double-anonymous and concurrent-submission checks, and filing correctly on HotCRP before a firm AoE deadline.

1k repo stars
▌
Oopsla Experiments · brycewang-stanford
Use when designing or auditing the evaluation of an OOPSLA paper — matching evidence type to claim type across the venue's spread (benchmarks, corpus studies, case studies, user studies, mechanized proofs), building baselines and workloads that survive the SIGPLAN checklist, and sizing experiments to the round calendar.

1k repo stars
▌
Oopsla Camera Ready · brycewang-stanford
Use when converting an accepted OOPSLA paper into its PACMPL journal article — final acmsmall formatting within the 25-page revision cap, de-anonymization and Data-Availability Statement updates, ACM open-access and rights steps, hitting the OOPSLA1 (April) or OOPSLA2 (October) issue, and planning the SPLASH talk.

1k repo stars
▌
Oopsla Related Work · brycewang-stanford
Use when building an OOPSLA related-work section — positioning against the PACMPL family (POPL, PLDI, ICFP, OOPSLA itself) plus ECOOP, Onward!, and SE venues, citing journal-era OOPSLA papers in PACMPL volume/issue form, verifying every venue attribution on dblp, and stating per-line technical deltas.

1k repo stars
▌
Oopsla Supplementary · brycewang-stanford
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.

1k repo stars
▌
Oopsla Writing Style · brycewang-stanford
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.

1k repo stars
▌
Oopsla Review Process · brycewang-stanford
Use when explaining or strategizing around OOPSLA's two-round review machinery — double-anonymous multi-stage reviewing, the four outcomes (Accept, Minor Revision, Major Revision, Reject), reviewer continuity across rounds, round-hopping a Major Revision, and how acceptance flows into a PACMPL issue and the SPLASH talk.

1k repo stars
▌
Oopsla Author Response · brycewang-stanford
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.

1k repo stars
▌
Oopsla Reproducibility · brycewang-stanford
Use when hardening an OOPSLA paper's empirical claims to the SIGPLAN Empirical Evaluation Guidelines — managed-runtime measurement discipline, warmup and variance reporting, corpus and benchmark provenance, environment pinning, and a Data-Availability Statement that the eventual artifact can actually honor.

1k repo stars
▌
Oopsla Artifact Evaluation · brycewang-stanford
Use when packaging an artifact for an accepted OOPSLA paper under the SPLASH artifact-evaluation track — surviving the kick-the-tires phase, earning the Functional and Reusable badges, depositing a Zenodo snapshot with a DOI for Available, and aligning artifact claims with the paper's Data-Availability Statement.

1k repo stars