asplos-artifact-evaluation
Use when preparing an ASPLOS artifact for the post-acceptance evaluation committee — writing the ae.tex Artifact Appendix with software/hardware/dataset dependencies, targeting the Available / Functional / Reproducible badges, archiving on a public repository, and planning the collaborative back-and-forth with evaluators.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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.
# ASPLOS Artifact Evaluation Artifact evaluation at ASPLOS is a post-acceptance, opt-in, **collaborative** process: an independent committee works with authors to validate the paper's key results, and successful artifacts carry badges on the published paper (AE pages, checked 2026-07-08). It is also a tradition the venue itself highlights — systems readers increasingly treat an unbadged systems paper as a weaker citation. Treat AE as part of the publication, budgeted like a small sixth section. ## The three badges and what each actually demands | Badge | 2027 criterion (paraphrased from the AE pages) | Practical bar | |---|---|---| | **Available** | Artifact placed on a **publicly accessible archival repository** | A DOI-issuing archive (institutional or Zenodo-class); a GitHub URL alone is not archival | | **Functional** | Evaluators can prepare and run the artifact; they document the steps they followed | Clean-machine install + a smoke experiment that completes in minutes, not hours | | **Reproducible** | Evaluators validate the paper's **key results** | Per-claim run scripts whose output maps visibly onto specific figures/tables | Evaluators assign scores per requested badge an
- The three badges and what each actually demands
- The Artifact Appendix is the contract
- Package layout that evaluators can navigate blind
- Hardware-dependent claims: give evaluators a path
- Collaboration protocol
- Common evaluator blockers, pre-empted
- Anonymity boundary
- Dry-run protocol
- Output format
What does the asplos-artifact-evaluation skill do?
Use when preparing an ASPLOS artifact for the post-acceptance evaluation committee — writing the ae.tex Artifact Appendix with software/hardware/dataset dependencies, targeting the Available / Functional / Reproducible badges, archiving on a public repository, and planning the collaborative back-and-forth with evaluators.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-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.