Explain Usage
asgeirtj/system_prompts_leaks
Explain where this session's tokens went, with one simple chart in plain language.
A skill your agent uses when explaining or strategizing around OOPSLA's two-round review machinery — double-anonymous multi-stage reviewing, the four outcomes (Accept, Minor Revision, Major…
MITAuto-check passed
Install Oopsla Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-review-process --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-review-process .claude/skills/oopsla-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-review-process into .claude/skills/oopsla-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-review-process", 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-review-processType 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-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-review-process --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-review-process .agents/skills/oopsla-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-review-process into .agents/skills/oopsla-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-review-process", 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-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-review-process --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-review-process .cursor/skills/oopsla-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-review-process into .cursor/skills/oopsla-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-review-process", 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-review-process--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-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-review-process --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-review-process .gemini/skills/oopsla-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-review-process into .gemini/skills/oopsla-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-review-process", 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-review-processInstalls 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-review-process -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-review-process .github/skills/oopsla-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-review-process into .github/skills/oopsla-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-review-process", 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-review-process -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-review-process --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-review-process .opencode/skills/oopsla-review-process && 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-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-review-process into .opencode/skills/oopsla-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-review-process", 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-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 495 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when explaining or strategizing around OOPSLA's two-round review machinery — double-anonymous multi-stage reviewing, the four outcomes (Accept, Minor Revision, Major…
- Works in 5 steps: Triage — format, anonymity, scope; the… → Multi-stage reviewing — the OOPSLA1 2026… → Author response — the four-day window… → …
- Strategizing around OOPSLAs two-round review machinery — double-anonymous multi-stage reviewing
- SKILL.md covers The four outcomes and what…, Round-hopping: the mechanic to…, Inside a round and Reading a review packet like a…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Oopsla Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
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
- Strategizing around OOPSLAs two-round review machinery — double-anonymous multi-stage reviewing
- The four outcomes (Accept
- Reviewer continuity across rounds
- Round-hopping a Major Revision
Example prompts
- “/oopsla-review-process”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Triage — format, anonymity, scope; the firm-deadline and 23-page rules
- Multi-stage reviewing — the OOPSLA1 2026 front matter describes
- Author response — the four-day window where bucket arguments happen
- Committee resolution — outcomes assigned; expectation lists drafted
- After acceptance — camera-ready into the PACMPL issue
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 Review Process loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 495 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). 495 words, ~1,124 tokens.
Download SKILL.mdSave it as
.claude/skills/oopsla-review-process/SKILL.md (or your agent's skills folder).- name
- oopsla-review-process
- description
- 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.
OOPSLA Review Process
OOPSLA reviews like a journal wearing a conference's clock. Two submission rounds per volume (2026: October 10, 2025 and March 17, 2026), a Review Committee whose chairs act as PACMPL Associate Editors (2026: Anders Møller and Işıl Dillig), multi-stage double-anonymous reviewing, an author-response window per round, and a four-way decision instead of a binary one. Round 1 of 2026 accepted 75 of 227 submissions into PACMPL Vol. 10, Issue OOPSLA1 — roughly a third, but treat any single round's rate as one data point, not a planning constant.
The four outcomes and what each really means
| Outcome | Mechanics | Author's correct read |
|---|---|---|
| Accept | Into the round's PACMPL issue after camera-ready | Deliver commitments; start the artifact |
| Minor Revision | Fixable concerns resolved within the same round's process (2026 folded the old Conditional Accept in here) | A near-accept with homework and a checker |
| Major Revision | Invitation to resubmit to the next round against an explicit expectations list, with reviewer continuity to the extent possible | The venue wants the paper — at its price |
| Reject | Out of this volume's pipeline | Diagnose before re-entering the SIGPLAN family |
The revision categories change meaningfully between volumes (the 2025→2026 merge is the proof), so restate the current definitions from the live track page before advising anyone.
Round-hopping: the mechanic to teach explicitly
A Major Revision is not a rejection with kind words — it is a reserved slot with named examiners. The hop works like this:
R1 submission (Oct) --Major Revision--> resubmit in R2 (Mar), same volume
R2 submission (Mar) --Major Revision--> resubmit in next volume's R1 (~Oct)
Either round --Accept/Minor Revision--> that round's issue (OOPSLA1 / OOPSLA2)Consequences worth spelling out:
- An R1 Major Revision handled well still publishes in the same year's volume (OOPSLA2) — often faster than a fresh submission elsewhere.
- An R2 Major Revision crosses volumes, so the calendar cost is ~7 months;
factor that into round choice at submission time (
oopsla-workflow). - Reviewer continuity cuts both ways: unresolved expectations are checked by the people who wrote them. Answer the list item by item in a change log; do not silently re-litigate demands you dislike — argue them explicitly or satisfy them.
Show full SKILL.md (173 more words)Show less
Inside a round
- Triage — format, anonymity, scope; the firm-deadline and 23-page rules
bite here (
oopsla-submission). - Multi-stage reviewing — the OOPSLA1 2026 front matter describes multiple stages of double-anonymous review; expect additional reviews or expert consultations on borderline papers between stages.
- Author response — the four-day window where bucket arguments happen
(
oopsla-author-response). - Committee resolution — outcomes assigned; expectation lists drafted for revision buckets.
- After acceptance — camera-ready into the PACMPL issue
(
oopsla-camera-ready), artifact evaluation with badges (oopsla-artifact-evaluation), talk at SPLASH.
Reading a review packet like a strategist
- Count, per review, the demands that are bounded (rerun, clarify, add baseline) versus unbounded (rethink the design, new study population). Mostly-bounded packets are Minor-Revision-shaped; argue accordingly.
- A single devastated reviewer among positive ones is a discussion problem, not a paper problem — your response should arm the positive reviewers with the citations and pointers they need to carry the argument.
- Fit complaints at OOPSLA are weaker than at narrower venues (the published scope spans formalisms to empirical studies); rebut them with precedent shapes, not indignation.
Output format
[Stage] triage / in review / response window / decision / revision pending
[Packet read] bounded vs unbounded demands per review
[Likely outcome] one of four + confidence
[Round plan] same-round path or hop target with dates from live pages
[Action] the single highest-leverage next move© 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-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Oopsla Review Process 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 Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Explain Usageasgeirtj/system_prompts_leaks | 69k | — | ~345 | Automated safety check: Pass | CC0-1.0 | |
| Strategic Compactaffaan-m/ECC | 276k | 2 repos | ~434 | Automated safety check: Pass | MIT | |
| Strategic Compactaffaan-m/ECC | 276k | 2 repos | ~724 | Automated safety check: Pass | MIT | |
| Strategic Compactaffaan-m/ECC | 276k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Strategic Compactaffaan-m/ECC | 276k | 3 repos | ~943 | Automated safety check: Pass | MIT |
Similar skills
Strategic Compact
affaan-m/ECC
任意の自動コンパクションではなく、タスクフェーズを通じてコンテキストを保持するための論理的な間隔での手動コンパクションを提案します。
Strategic Compact
affaan-m/ECC
임의의 자동 컴팩션 대신 논리적 간격에서 수동 컨텍스트 압축을 제안하여 작업 단계를 통해 컨텍스트를 보존합니다.
Strategic Compact
affaan-m/ECC
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
Strategic Compact
affaan-m/ECC
建议在逻辑间隔处手动压缩上下文，以在任务阶段中保留上下文，而非任意的自动压缩。
Logic Explain
sickn33/agentic-awesome-skills
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions).
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 Review Process
What does Oopsla Review Process do?
A skill your agent uses when explaining or strategizing around OOPSLA's two-round review machinery — double-anonymous multi-stage reviewing, the four outcomes (Accept, Minor Revision, Major…. Oopsla Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Oopsla Review Process?
Oopsla Review Process fits situations like: strategizing around OOPSLAs two-round review machinery — double-anonymous multi-stage reviewing; the four outcomes (Accept; reviewer continuity across rounds; round-hopping a Major Revision.
How do I install Oopsla Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-review-process -a claude-code`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/oopsla-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Oopsla Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-review-process -a codex`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/oopsla-review-process in your project. Codex loads it when a task matches its description.
Can I use Oopsla Review Process 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-review-process -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-review-process, .gemini/skills/oopsla-review-process, .github/skills/oopsla-review-process and .opencode/skills/oopsla-review-process in your project.
What does Oopsla Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Oopsla Review Process is instructions for the agent only.
Does Oopsla Review Process 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 Review Process 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 Review Process use?
Oopsla Review Process 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 Review Process use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Review Process?
Skills that share tags, products or a category with Oopsla Review Process: Explain Usage (asgeirtj/system_prompts_leaks, 69k stars), Strategic Compact (affaan-m/ECC, 276k stars), Strategic Compact (affaan-m/ECC, 276k stars) and Strategic Compact (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oopsla Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.