isca-artifact-evaluation
Use when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets, packaging simulator-heavy workflows others can run, writing the evaluator-facing appendix, and earning badges that print on the paper.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.
# ISCA Artifact Evaluation The verified 2026 arrangement: authors of **accepted** papers could voluntarily submit artifacts, assessed under the **ACM Artifact Review and Badging** policy, with earned badges printed on the paper and attached as ACM Digital Library metadata — and with no effect on the acceptance decision itself. The conference framed AE as a recent, deliberate import into the architecture community (following ASPLOS from 2020 and MICRO from 2021). Voluntary does not mean optional in practice: badges are becoming the community's default trust signal, and an architecture paper without them increasingly gets asked why. ## Decide scope first: which claims does the artifact defend? Architecture artifacts fail most often from over-promising. Before packaging, split the paper's results three ways and say so in the artifact documentation: | Tier | Contents | Evaluator experience | |---|---|---| | **Reproduce** | Headline figure(s) + key ablation, runnable on evaluator-accessible machines within hours | Runs it, matches within stated tolerance | | **Regenerate-with-resources** | Full sweeps needing cluster-days; scripts and configs complete, cost stated honestly | Inspects, s
- Decide scope first: which claims does the artifact defend?
- Simulator-heavy artifacts: the specific frictions
- The package an evaluator can drive blind
- The badge set under ACM's policy
- Working with evaluators
- Timing and division of labor
- Submission gate
Cold-start rehearsal — run on a machine that has never seen the project docker load < artifact-image.tar.gz docker run --rm -it artifact:v1 bash -lc './run_all.sh --tier reproduce' diff <(csvcut -c workload,ipc results/f07.csv) \
What does the isca-artifact-evaluation skill do?
Use when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets, packaging simulator-heavy workflows others can run, writing the evaluator-facing appendix, and earning badges that print on the paper.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.