Judge
NeoLabHQ/context-engineering-kit
Launch a meta-judge then a judge sub-agent to evaluate results produced in the current conversation
A skill your agent uses when judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design, implementation, formalism, or empirical study — and routing within the…
MITAuto-check passed
Install Oopsla Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-topic-selection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/OOPSLA-Skills/skills/oopsla-topic-selection .claude/skills/oopsla-topic-selection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "oopsla-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selection into .claude/skills/oopsla-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-topic-selection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-topic-selection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/OOPSLA-Skills/skills/oopsla-topic-selection .agents/skills/oopsla-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oopsla-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selection into .agents/skills/oopsla-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-topic-selection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-topic-selection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/OOPSLA-Skills/skills/oopsla-topic-selection .cursor/skills/oopsla-topic-selection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oopsla-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selection into .cursor/skills/oopsla-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-topic-selection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path OOPSLA-Skills/skills/oopsla-topic-selection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-topic-selection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/OOPSLA-Skills/skills/oopsla-topic-selection .gemini/skills/oopsla-topic-selection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oopsla-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selection into .gemini/skills/oopsla-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-topic-selection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-topic-selectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/OOPSLA-Skills/skills/oopsla-topic-selection .github/skills/oopsla-topic-selection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oopsla-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selection into .github/skills/oopsla-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-topic-selection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-topic-selection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/OOPSLA-Skills/skills/oopsla-topic-selection .opencode/skills/oopsla-topic-selection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oopsla-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-topic-selection into .opencode/skills/oopsla-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-topic-selection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oopsla-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 456 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design, implementation, formalism, or empirical study — and routing within the…
- Judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design
- SKILL.md covers The center-of-mass test, Signals the project is…, Signals to route away and Two-round consequence for…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Empirical study — and routing within the SIGPLAN family from OOPSLAs seat: POPL for theory-first
What it does
Oopsla Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design
- Empirical study — and routing within the SIGPLAN family from OOPSLAs seat: POPL for theory-first
- PLDI for implementation-performance
- ICFP for functional
Example prompts
- “/oopsla-topic-selection”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Oopsla Topic Selection loads about 1.1k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 456 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 456 words, ~1,107 tokens.
Download SKILL.mdSave it as
.claude/skills/oopsla-topic-selection/SKILL.md (or your agent's skills folder).- name
- oopsla-topic-selection
- description
- 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.
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 without full evidence | Onward! (same SPLASH building) | Evidence has matured past position-paper strength |
| OO language design, European community | ECOOP (AITO, not PACMPL) | PACMPL journal publication or the SPLASH audience matters |
| Testing/analysis practice at SE scale | ISSTA / ICSE / FSE | The finding changes how languages are designed, not just tools |
| Human factors of programming | CHI or OOPSLA's human-aspects lane | The methodology meets study-design scrutiny (oopsla-experiments) |
Signals the project is genuinely OOPSLA-shaped
- The contribution couples layers — a semantics plus its implementation consequences, a design plus the empirical study of its use — rather than living purely in one.
- The paper would still matter if a competing implementation shipped: the claim is about the design space, not the artifact's existence.
- Experience and applications carry analysis: OOPSLA has a real lane for "we built and deployed it; here is what generalizes" (the Julia paper is the model), which PLDI/POPL reward less.
- Empirical questions about programs and programmers at scale — adoption, API misuse, bug taxonomies — with instrument-grade methodology.
Show full SKILL.md (141 more words)Show less
Signals to route away
- The evaluation is the contribution and it's a speedup: PLDI's benchmark-first culture is the better courtroom.
- The theorem stands alone without an implementation story: POPL.
- The idea needs permission to be speculative: Onward!, and return to OOPSLA a volume later with evidence — a deliberate SPLASH-internal pipeline.
- The novelty is a product description: no SIGPLAN venue; consider an industry track or experience venue outside the family.
Two-round consequence for routing
Because OOPSLA offers two doors a year with a revision system, it is often
the fastest family member from "solid evidence" to "published journal
article" — a legitimate tiebreaker when a paper fits two venues. It is a bad
reason to submit work whose center of mass is elsewhere: family reviewer
pools overlap heavily, and a misrouted paper burns goodwill you will meet
again (oopsla-review-process).
Decision procedure
1. Write the one-sentence claim; identify its center of mass (table above)
2. Check exemplar precedent: which library entry shape matches? none → doubt
3. Ask the coupling question: does the paper bridge ≥2 layers? no → sibling
4. Verify current scope text on the live track page (topics drift by volume)
5. Commit to a round (oopsla-workflow) or a re-route with a named venueOutput format
[Center of mass] <one sentence + layer(s) it lives in>
[Routing] OOPSLA / POPL / PLDI / ICFP / Onward! / ECOOP / SE venue / other
[Precedent] exemplar shape matched, or none
[Fit risk] the objection the committee would raise
[Commitment] target round or re-route action© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in OOPSLA-Skills/skills/oopsla-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Oopsla Topic Selection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oopsla Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| JudgeNeoLabHQ/context-engineering-kit | 1.7k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Do And JudgeNeoLabHQ/context-engineering-kit | 1.7k | — | ~14k | Automated safety check: Pass | GPL-3.0 | |
| TopicsZimoLiao/scholaraio | 576 | — | ~294 | Automated safety check: Pass | MIT | |
| Topic Modelingbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Add Shape Inferenceonnx/onnx | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Do And Judge
NeoLabHQ/context-engineering-kit
Execute a task with sub-agent implementation and LLM-as-a-judge verification with automatic retry loop
Topics
ZimoLiao/scholaraio
A skill your agent uses when the user asks about research themes, topic distribution, BERTopic clustering, topic overview, topic papers, topic merges, or HTML topic visualizations.
Topic Modeling
brycewang-stanford/Auto-Empirical-Research-Skills
Structural topic modeling: STM spec, topic count, coherence-exclusivity.
Add Shape Inference
onnx/onnx
Add or update type and shape inference for an ONNX operator.
Bestblogs Topic
ginobefun/BestBlogs
A skill your agent uses when the user asks about a specific topic, subject area, or wants to explore curated topic pages on BestBlogs.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Oopsla Topic Selection
What does Oopsla Topic Selection do?
A skill your agent uses when judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design, implementation, formalism, or empirical study — and routing within the…. Oopsla Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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!
When should I use Oopsla Topic Selection?
Oopsla Topic Selection fits situations like: judging whether a project is OOPSLA-shaped — a PL contribution whose evidence spans design; empirical study — and routing within the SIGPLAN family from OOPSLAs seat: POPL for theory-first; PLDI for implementation-performance; ICFP for functional.
How do I install Oopsla Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a claude-code`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/oopsla-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Oopsla Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a codex`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/oopsla-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Oopsla Topic Selection in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oopsla-topic-selection, .gemini/skills/oopsla-topic-selection, .github/skills/oopsla-topic-selection and .opencode/skills/oopsla-topic-selection in your project.
What does Oopsla Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Oopsla Topic Selection is instructions for the agent only.
Does Oopsla Topic Selection access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Oopsla Topic Selection safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Oopsla Topic Selection use?
Oopsla Topic Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Oopsla Topic Selection use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Oopsla Topic Selection?
Skills that share tags, products or a category with Oopsla Topic Selection: Judge (NeoLabHQ/context-engineering-kit, 1.7k stars), Do And Judge (NeoLabHQ/context-engineering-kit, 1.7k stars), Topics (ZimoLiao/scholaraio, 576 stars) and Topic Modeling (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oopsla Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.