oopsla-artifact-evaluation
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-artifact-evaluation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OOPSLA Artifact Evaluation SPLASH runs a unified artifact-evaluation track for its research papers; the 2026 edition used a **two-phase** process — an opening *kick-the-tires* pass where evaluators check the artifact builds and starts at all, then the full evaluation — awarding **Functional** (documented, complete enough to exercise), **Reusable** (Functional plus organization and documentation that support reuse by others), and **Available** (a snapshot deposited on Zenodo with a DOI), with Available strongly encouraged for every passing artifact absent licensing or privacy constraints. Per-cycle dates and submission mechanics live on the current track page (待核实 each cycle). ## Design for the kick-the-tires failure mode Most artifacts that miss a badge die in the first hour of a stranger's time: a build that assumes your machine. The discipline is to treat the evaluator as a hostile fresh VM. ```text Golden-path contract (put this at the top of README.md): 1. Requirements: OS/arch, RAM, disk, expected wall-clock time 2. One command to build (container image or pinned toolchain) 3. One command for a 10-minute smoke result mapped to a named claim 4. One command per paper table/fig
- Design for the kick-the-tires failure mode
- Badge strategy
- Claim-to-artifact mapping
- Scope and timing notes
- Output format
What does the oopsla-artifact-evaluation skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill oopsla-artifact-evaluation --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.