osdi-reproducibility
Use when building reproducibility into an OSDI systems project — recording hardware, configuration, workload, and measurement provenance while experiments run, keeping paper and artifact from drifting apart, and setting up for the post-acceptance sysartifacts evaluation and open-access scrutiny.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-reproducibility --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.
# OSDI Reproducibility Make the numbers survivable. OSDI-specific hooks below (artifact timing, badge scope, open-access exposure) are 2026-cycle facts verified 2026-07-08; the provenance discipline is venue-independent engineering. ## Why the bar is high at OSDI specifically Two venue mechanics raise the stakes beyond generic good practice: - **USENIX proceedings are open access from day one.** Every reader on the internet — including the teams whose systems you outperformed — gets the free PDF immediately and can attempt your numbers. Errors get found publicly and fast. - **Artifact evaluation happens after acceptance** (May 8, 2026, 8:59 pm PDT in the '26 cycle), when the experiments are months old. If provenance was not recorded while runs happened, the artifact reconstructs a memory, not an experiment. Reproducibility at OSDI is therefore a *recording* problem during the project, not a *packaging* problem at the end. Packaging is `osdi-artifact-evaluation`'s job; this skill makes packaging possible. ## The provenance ledger Maintain one machine-readable ledger, committed beside the code, updated by the run scripts themselves — never by hand after the fact: ```yaml # runs/2025-
- Why the bar is high at OSDI specifically
- The provenance ledger
- What systems papers must pin down
- Determinism where it is cheap, honesty where it is not
- Traces, data, and the licensing wall
- Timing against the 2026 cycle
- The handoff test
- Output format
What does the osdi-reproducibility skill do?
Use when building reproducibility into an OSDI systems project — recording hardware, configuration, workload, and measurement provenance while experiments run, keeping paper and artifact from drifting apart, and setting up for the post-acceptance sysartifacts evaluation and open-access scrutiny.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-reproducibility --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.