Menu

Individual skill

fast-reproducibility

0upvotes

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.

FAST-Skills/skills/fast-reproducibility/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,411
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top