mlsys-artifact-evaluation
Use when packaging an accepted MLSys paper's code, configs, and measurement scripts for the venue's post-acceptance artifact evaluation, targeting the Availability, Functional, and Reproducible badges, writing the Artifact Appendix, handling hardware that AE reviewers cannot access, and answering anonymous evaluator questions.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.
# MLSys Artifact Evaluation Use this after acceptance, when deciding whether and how to enter MLSys artifact evaluation. AE is one of this venue's defining institutions: a separate committee evaluates how well artifacts support the paper's claims and awards badges. In the 2026 cycle (verified 2026-07-08): submission of artifact abstract, paper PDF, and Artifact Appendix to a dedicated AE site by March 8; evaluation window March 8 - April 8; badges for **Availability**, **Functional**, and **Reproducible**; anonymous reviewer-author interaction during evaluation; and a small number of Distinguished Artifact Awards for exceptional packages. Reopen the current Call for Artifact Evaluations before relying on any of these mechanics. ## Badge strategy — decide the target first | Badge | What evaluators check | Typical cost to authors | |---|---|---| | Availability | Artifact is publicly and permanently retrievable (public GitHub-style link expected in the appendix) | Hours: license, public repo, archival snapshot | | Functional | The artifact runs: documented, complete relative to the paper, exercisable end-to-end | Days: install path, smoke test, small-scale example | | Reproducible | E
- Badge strategy — decide the target first
- The hardware problem — MLSys AE's hardest part
- Package skeleton evaluators expect
- Artifact Appendix skeleton
- During the evaluation window
- Why bother
- Cycle-volatility warnings
- Output format
What does the mlsys-artifact-evaluation skill do?
Use when packaging an accepted MLSys paper's code, configs, and measurement scripts for the venue's post-acceptance artifact evaluation, targeting the Availability, Functional, and Reproducible badges, writing the Artifact Appendix, handling hardware that AE reviewers cannot access, and answering anonymous evaluator questions.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.