nsdi-artifact-evaluation
Use when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for the Community Award.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-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.
# NSDI Artifact Evaluation Artifact evaluation at NSDI is post-acceptance and opt-in: accepted authors package what the paper is made of, an Artifact Evaluation Committee tries it, and earned badges travel with the paper. Mechanics below follow the NSDI '26 Call for Artifacts as rendered on 2026-07-08 — the '27 call was not yet retrievable (待核实), so treat '26 as the model and reread the live page after acceptance. ## What the '26 cycle established - Evaluation was **open to all accepted papers**. - **Three separate badges**; a paper may earn one, two, or all three. The confirmed name is **Artifacts Available** — awarded when artifacts are retrievable **permanently and publicly**, with Zenodo encouraged (public funding, DOI assignment). The other two badge names in the NSDI '26 wording were not fully retrievable (待核实); USENIX's scheme at sibling venues pairs Available with functionality and results-reproduction badges. - **Authors choose** which badges the AEC should consider at artifact-submission time — the evaluation is scoped to what you claim. - '26 timeline anchor: artifacts due **July 31, 2025**, decisions **October 14, 2025** — i.e., months after the first acceptance cohort,
- What the '26 cycle established
- Choose badges like claims
- The Community Award changes your timeline
- Package for a stranger with a deadline
- Dry-run protocol before submission
- Process notes
- Common failure modes at systems AECs
- Output format
What does the nsdi-artifact-evaluation skill do?
Use when preparing an accepted NSDI paper's artifact for badge evaluation — packaging code, traces, and testbed recipes for the AEC, choosing which badges to pursue, meeting Zenodo-style permanence expectations, and timing public release to stay eligible for the Community Award.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-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.