osdi-artifact-evaluation
Use when preparing an OSDI artifact for sysartifacts-run evaluation — the post-acceptance timeline, the 2026 narrowing to a single Artifacts Available badge, Zenodo-grade permanent archiving, the AE-committee runbook, and the two-page Artifact Appendix that documents the result.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-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.
# OSDI Artifact Evaluation Package the system for the artifact evaluation committee (AEC). Everything cycle-specific below is OSDI '26 as verified 2026-07-08 — and 2026 changed the rules, so check the live Call for Artifacts (`usenix.org/conference/osdi26/call-for-artifacts` pattern) before optimizing for the wrong target. ## How OSDI AE is wired - **Who:** an AEC organized with the **sysartifacts** community (`sysartifacts.github.io`), which runs artifact evaluation across the systems conferences — reviewers are systems students and researchers on machines that are not yours. - **When:** artifacts are submitted **after the paper is (conditionally) accepted** — the '26 deadline was **May 8, 2026, 8:59 pm PDT**, about six weeks after the March 26 notification. The chairs explicitly encouraged preparing the artifact while the paper was still under review; teams that ignored this spent April in a panic. - **Stakes:** badges appear on the published paper. AE is optional but has become an expectation for systems papers claiming practical relevance — and it is the prerequisite for the final paper's two-page Artifact Appendix. ## The 2026 badge narrowing | Cycle | Badges evaluated | |---|
- How OSDI AE is wired
- The 2026 badge narrowing
- Artifact anatomy
- Systems-specific honesty
- Working with the AEC
- From badge to Artifact Appendix
- Output format
What does the osdi-artifact-evaluation skill do?
Use when preparing an OSDI artifact for sysartifacts-run evaluation — the post-acceptance timeline, the 2026 narrowing to a single Artifacts Available badge, Zenodo-grade permanent archiving, the AE-committee runbook, and the two-page Artifact Appendix that documents the result.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill osdi-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.