vldb-artifact-evaluation
Use when preparing a PVLDB artifact for the pVLDB Reproducibility Evaluation or the ACM availability badge, covering the mandatory participation rule for EA&B papers, the four artifact surfaces evaluators rebuild, packaging for a rerun by strangers, and positioning for the Best Reproducible Paper Award at VLDB.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-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.
# VLDB Artifact Evaluation Use this once a PVLDB paper is accepted (or when an EA&B submission is being planned, since participation is not optional there). The pVLDB Reproducibility Evaluation — run jointly with SIGMOD's effort since the 2018 push — has committee members rebuild your experiment from your package. Two distinct prizes exist: the ACM **availability** badge for sharing, and the **Reproducible** outcome (with a Best Reproducible Paper Award) for surviving an independent rerun. ## Who must play, who should | Situation | Obligation | |---|---| | EA&B paper | Required: release all data and software, submit to evaluation | | Regular research paper | Optional but strongly encouraged; badge on offer | | Industrial paper with proprietary core | Availability of what can be shared; document the rest | | Vision paper | Rarely applicable | ## The four surfaces evaluators rebuild The committee's published expectations decompose an artifact into four layers. Package each one explicitly: 1. **Prototype** — source code, build environment, configuration. A container image plus the Dockerfile that produced it is the community's default. 2. **Input data** — the datasets themselves, or d
- Who must play, who should
- The four surfaces evaluators rebuild
- Design for a stranger's machine
- Minimal package skeleton
- Award positioning
- Output format
What does the vldb-artifact-evaluation skill do?
Use when preparing a PVLDB artifact for the pVLDB Reproducibility Evaluation or the ACM availability badge, covering the mandatory participation rule for EA&B papers, the four artifact surfaces evaluators rebuild, packaging for a rerun by strangers, and positioning for the Best Reproducible Paper Award at VLDB.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-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 984 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.