Agent skill · Design & Presentation

oopsla-topic-selection

Use when judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design, implementation, formalism, or empirical study — and routing within the SIGPLAN family from OOPSLA's seat: POPL for theory-first, PLDI for implementation-performance, ICFP for functional, Onward! for vision, ECOOP, or SE venues.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: OOPSLA-Skills/skills/oopsla-topic-selection/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# OOPSLA Topic Selection OOPSLA is the broadest seat at the SIGPLAN table: its published scope covers programming languages "from design to implementation and from mathematical formalisms to empirical studies," and its verified exemplars include a benchmark suite, a measurement-methodology critique, a corpus/survey study, a soundness counterexample, a language experience report, and a formalized runtime mechanism (`resources/exemplars/library.md`). The routing question is therefore rarely "is this PL?" but "is OOPSLA's *breadth* the asset, or would a narrower sibling reward this paper's center of mass more?" ## The center-of-mass test State the one sentence a reviewer would repeat to the committee. Route on what that sentence *is about*: | The sentence is about... | First-choice venue | OOPSLA case exists when... | | --- | --- | --- | | A metatheoretic result, calculus, logic | POPL | The formalism explains a deployed mechanism or design choice | | Compiler/runtime performance engineering | PLDI | The insight is the design trade-off, not the speedup | | Typed/functional language technique | ICFP | The audience is OO/imperative/multi-paradigm practice | | A provocative vision withou

What's inside
Steps it walks through
  1. The center-of-mass test
  2. Signals the project is genuinely OOPSLA-shaped
  3. Signals to route away
  4. Two-round consequence for routing
  5. Decision procedure
  6. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the oopsla-topic-selection skill do?

Use when judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design, implementation, formalism, or empirical study — and routing within the SIGPLAN family from OOPSLA's seat: POPL for theory-first, PLDI for implementation-performance, ICFP for functional, Onward! for vision, ECOOP, or SE venues.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection --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.

Keep going