micro-reproducibility
Use when hardening a MICRO paper's results for re-derivation — pinning simulator commits and configs, recording workload trace provenance and SimPoint recipes, versioning power/area models, capturing RTL toolchain state, and writing the run manifests that later survive MICRO's post-acceptance artifact evaluation.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-reproducibility --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 Reproducibility In microarchitecture research the "experiment" is usually a software artifact pretending to be hardware. That makes results *perfectly* reproducible in principle — and silently unreproducible in practice, because a simulator commit, a config diff, or a trace-generation flag changed between the headline run and the camera-ready. This skill installs the record-keeping that prevents that. ## What must be pinned, by evidence type | Evidence | Pin these or the number is unrecoverable | |---|---| | Cycle-level simulation | Simulator name + exact commit hash; full config files (not "8-wide OoO" prose); patch set applied; host compiler for the simulator build | | Workload traces | Source binary + compiler flags; trace tool + version; SimPoint interval size, K, and seed; warmup instructions per region | | Power / area estimates | McPAT/CACTI/Accelergy version; technology node; the XML/cfg input actually fed in; any manual scaling factors | | RTL results | HDL commit; synthesis tool + version; target library/PDK; constraints file; which corners were run | | FPGA / silicon | Board/chip stepping; bitstream hash or firmware; frequency; measurement method for power (rail
- What must be pinned, by evidence type
- The run manifest
- Disclosure lines the paper itself owes
- Determinism and drift checks
- Validating the instrument itself
- Anonymity interaction (submission phase)
- Storage economics of keeping everything
- Output format
What does the micro-reproducibility skill do?
Use when hardening a MICRO paper's results for re-derivation — pinning simulator commits and configs, recording workload trace provenance and SimPoint recipes, versioning power/area models, capturing RTL toolchain state, and writing the run manifests that later survive MICRO's post-acceptance artifact evaluation.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-reproducibility --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.