fast-reproducibility
Use when strengthening USENIX FAST reproducibility and open-science evidence, covering device and firmware provenance, device-state disclosure, trace availability and replay, claim-to-evidence mapping, honest degrees of reproducibility on hardware that ages and varies, and consistency between what the paper says and what the artifact contains.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-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.
# FAST Reproducibility Use this before submission and again before camera-ready. FAST's storage results live on **real hardware that ages, throttles, and varies part-to-part**, so reproducibility here is a distinct craft from software-only venues: a reader reproducing your work needs to know not just the code but the *device, its firmware, and its state*. The goal is that a competent reader with comparable hardware could rebuild your evidence and reach your conclusions. ## Evidence map - Map each claim and reported number to a **verifiable location** — a paper section, a table generated from a logged run, or a script in the artifact. - For a system, give enough of the design, parameters, mkfs/mount options, and build environment that a reader could rebuild and run it. - For measurements, report the **device provenance** (models, firmware, interface), the **host** (CPU, RAM, kernel), and the **device state** (steady-state/aged, fill, TRIM) — the storage-only provenance that software artifacts omit. - Keep the **availability statement** truthful and specific: what code and traces are shared, where they will live after acceptance, and — if something cannot be shared — exactly why. - K
- Evidence map
- Availability statement audit
- Provenance pinning
- Degrees of reproducibility (state the one you achieved)
- The hardware-variance caveat (state it plainly)
- Vignette: a file-system aging study
- Consistency and camera-ready pass
- Output format
What does the fast-reproducibility skill do?
Use when strengthening USENIX FAST reproducibility and open-science evidence, covering device and firmware provenance, device-state disclosure, trace availability and replay, claim-to-evidence mapping, honest degrees of reproducibility on hardware that ages and varies, and consistency between what the paper says and what the artifact contains.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-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 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.