micro-artifact-evaluation
Use when preparing a MICRO artifact for post-acceptance evaluation — packaging simulators, configs, traces, and scripts so evaluators can regenerate the paper's figures, targeting the ACM Available/Functional/Reproducible badges, handling licensed workloads and long simulations, and earning the optional artifact appendix.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.
# MICRO Artifact Evaluation MICRO runs artifact evaluation **after acceptance**: authors of accepted papers are invited to submit artifacts, an Artifact Evaluation Committee reviews them, and successful papers carry ACM badges in the proceedings. Anchors here are the MICRO 2025 AE pages (`micro58/submit/artifacts.php`, verified 2026-07-08); the 2026 edition's AE page and calendar are 待核实 — expect the same architecture, verify the dates. ## Badge targets and what each demands | Badge (ACM) | Bar | Microarchitecture-specific gotcha | |---|---|---| | Artifact Available | Deposited on a **public archival repository** — Zenodo, FigShare, Dryad named in 2025 | A GitHub repo alone fails; it is not archival. Deposit a tagged snapshot, keep GitHub as the living mirror | | Artifact Functional | Documented, complete, exercisable | Simulator builds on a clean machine — your decade of dotfiles is not in the package | | Results Reproducible | Evaluators regenerate the paper's main claims | Simulation *time* is the enemy: full SPEC runs take days-weeks; provide a subset path | Papers passing AE also earned, in 2025, the right to a **two-page artifact appendix in the camera-ready, free of charge**
- Badge targets and what each demands
- The time-budget problem is the design problem
- Package inventory
- Licensed and unshippable inputs
- Common failure modes, ranked by frequency of pain
- Working with evaluators
- Minimal artifact layout that evaluators navigate well
- Output format
What does the micro-artifact-evaluation skill do?
Use when preparing a MICRO artifact for post-acceptance evaluation — packaging simulators, configs, traces, and scripts so evaluators can regenerate the paper's figures, targeting the ACM Available/Functional/Reproducible badges, handling licensed workloads and long simulations, and earning the optional artifact appendix.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.