Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
A skill your agent uses 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…
Install Oopsla Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-related-work --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-related-work .claude/skills/oopsla-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-related-work into .claude/skills/oopsla-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-related-work --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-related-work .agents/skills/oopsla-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-related-work into .agents/skills/oopsla-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-related-work --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-related-work .cursor/skills/oopsla-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-related-work into .cursor/skills/oopsla-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills oopsla-related-work --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-related-work .gemini/skills/oopsla-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-related-work into .gemini/skills/oopsla-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/oopsla-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-related-work into .github/skills/oopsla-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/oopsla-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/OOPSLA-Skills/skills/oopsla-related-work into .opencode/skills/oopsla-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oopsla-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 403 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Building an OOPSLA related-work section — positioning against the PACMPL family (POPL
- SKILL.md covers Citation form in the journal era, Verification discipline, Deltas, not inventories and Coverage strategy, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- OOPSLA itself) plus ECOOP
What it does
Oopsla Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Literature review. 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
- Building an OOPSLA related-work section — positioning against the PACMPL family (POPL
- OOPSLA itself) plus ECOOP
- Citing journal-era OOPSLA papers in PACMPL volume/issue form
- Verifying every venue attribution on dblp
Example prompts
- “/oopsla-related-work”
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 (its code samples are bibtex).
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 Related Work loads about 1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 403 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). 403 words, ~1,000 tokens.
Download SKILL.mdSave it as
.claude/skills/oopsla-related-work/SKILL.md (or your agent's skills folder).- name
- oopsla-related-work
- description
- 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.
OOPSLA Related Work
OOPSLA sits inside a family that shares authors and reviewers: POPL, PLDI, ICFP publish in the same PACMPL journal, ECOOP is the adjacent European OO venue, Onward! shares the SPLASH building, and ICSE/FSE/ISSTA overlap on empirical software questions — ISSTA was literally co-located with SPLASH 2026. The related-work section is therefore written for people who may have authored the cited lines, and who will meet your paper again if a revision round occurs. Two failure modes dominate: venue misattribution and delta-free citation lists.
Citation form in the journal era
Since OOPSLA became a PACMPL track, its papers are journal articles and must be cited as such:
@article{belyakova2020worldage,
author = {Belyakova, Julia and Chung, Benjamin and Gelinas, Jack
and Nash, Jameson and Tate, Ross and Vitek, Jan},
title = {World Age in Julia: Optimizing Method Dispatch
in the Presence of Eval},
journal = {Proc. ACM Program. Lang.},
volume = {4},
number = {OOPSLA},
articleno = {207},
year = {2020},
doi = {10.1145/3428275}
}Recent volumes split into OOPSLA1 and OOPSLA2 issues — preserve the issue
name (number = {OOPSLA1}) exactly as the ACM DL records it. Citing a PACMPL
article as "In OOPSLA '24" is the kind of sloppiness family reviewers notice
in their own papers' entries.
Verification discipline
Every venue claim gets checked, not remembered:
| Check | Tool | What it catches |
|---|---|---|
dblp key (conf/oopsla/ or journals/pacmpl/) | dblp search | PLDI/POPL/ECOOP results misfiled as OOPSLA (see the cut list in resources/exemplars/library.md) |
| DOI resolves to claimed venue | ACM DL | Preprint-vs-published divergence; wrong-year citations |
| Issue OOPSLA1 vs OOPSLA2 | ACM DL table of contents | Half-year attribution errors in recent work |
| Sibling series coverage | Per-venue dblp streams | The "we searched OOPSLA only" blind spot |
Show full SKILL.md (182 more words)Show less
Deltas, not inventories
The family's standard is one technical difference per cited line of work, in the sentence where the citation appears:
- Weak: "Ownership types have been widely studied [3,7,12,19]."
- Strong: "[3] and [7] assume whole-program annotation; [12] recovers partial soundness but reports blame at the failure site rather than the boundary; we prove boundary blame is the weakest sound choice (§3)."
For concurrent work surfacing in the other round of the same volume — a genuinely OOPSLA-specific situation — cite it, mark it concurrent, and state the relationship without claiming priority; reviewer continuity means the committee likely knows both papers.
Coverage strategy
- Sweep the last three volumes of PACMPL Issues OOPSLA1/OOPSLA2, plus the matching POPL/PLDI/ICFP issues, before declaring novelty.
- Add ECOOP and the relevant SE venue (ICSE/FSE/ISSTA) whenever the claim is empirical or tooling-facing; add TOPLAS/JFP for journal-depth lines.
- Onward! papers are citable idea-stage precedents: acknowledging one costs nothing and omitting one your reviewer wrote costs a lot.
- Keep a claims-to-prior-work matrix in the repo; regenerate it at each round, because seven months pass between rounds and the family publishes continuously.
Output format
[Attribution audit] entries checked on dblp/DL: n/n, errors: <list>
[Citation form] PACMPL journal form used for post-2017 OOPSLA: yes/no
[Delta coverage] cited lines with explicit deltas: n/m + worst offenders
[Family sweep] OOPSLA/POPL/PLDI/ICFP/ECOOP/SE volumes covered
[Concurrent work] same-volume-round items flagged and handled© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Oopsla Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence |
Similar skills
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
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…
Related
Categories
Questions about Oopsla Related Work
What does Oopsla Related Work do?
A skill your agent uses 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 Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills., 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.
When should I use Oopsla Related Work?
Oopsla Related Work fits situations like: building an OOPSLA related-work section — positioning against the PACMPL family (POPL; OOPSLA itself) plus ECOOP; citing journal-era OOPSLA papers in PACMPL volume/issue form; verifying every venue attribution on dblp.
How do I install Oopsla Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-related-work -a claude-code`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/oopsla-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Oopsla Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-related-work -a codex`. Or copy the skill folder (OOPSLA-Skills/skills/oopsla-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/oopsla-related-work in your project. Codex loads it when a task matches its description.
Can I use Oopsla Related Work 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-related-work -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-related-work, .gemini/skills/oopsla-related-work, .github/skills/oopsla-related-work and .opencode/skills/oopsla-related-work in your project.
What does Oopsla Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Oopsla Related Work is instructions for the agent only.
Does Oopsla Related Work 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 Related Work 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 Related Work use?
Oopsla Related Work 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 Related Work use?
About 1k tokens (SKILL.md is roughly 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 Related Work?
Skills that share tags, products or a category with Oopsla Related Work: Nature Paper Card (Yuan1z0825/nature-skills, 47k stars), Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars) and Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oopsla Related Work?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.