fast-artifact-evaluation
Use when packaging a USENIX FAST artifact for the USENIX Artifact Evaluation scheme (Artifacts Available, Artifacts Functional, Results Reproduced), covering what a storage AEC checks first, DOI-issuing archives, the artifact appendix, and the special challenges of storage artifacts that need specific devices, large traces, or long endurance runs on the separate post-acceptance timeline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-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.
# FAST Artifact Evaluation Use this for the artifact track. FAST follows the **USENIX artifact-evaluation** model, and evaluation is a **separate, post-acceptance** process with its own timeline and an Artifact Evaluation Committee (AEC). Two things to internalize: badges are earned by evaluators actually using your package, and the review-time artifact (anonymized, for the paper's reviewers) is not the same deliverable as the badge artifact (de-anonymized, permanently archived, with an artifact appendix). ## The three USENIX badges (verify the current set and names) | Badge | What it certifies | What earns it | |---|---|---| | Artifacts Available | The artifact is permanently, publicly retrievable | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) | | Artifacts Functional | The artifact works and is useful for the paper's outcomes | A documented build/run, a demo, and expected outputs on the AEC's setup | | Results Reproduced | An evaluator reproduced the paper's main results | A path from the artifact to the headline numbers | Available is a low-cost, high-value badge (archive the package). Functional and Reproduced require the evaluator's own run to succeed
- The three USENIX badges (verify the current set and names)
- The storage-artifact problem: hardware dependence
- What a storage AEC opens first
- Packaging plan
- Anonymized review artifact vs. badge artifact
- Worked vignette: packaging a KV-store + measurement study
- Calibration
- Output format
What does the fast-artifact-evaluation skill do?
Use when packaging a USENIX FAST artifact for the USENIX Artifact Evaluation scheme (Artifacts Available, Artifacts Functional, Results Reproduced), covering what a storage AEC checks first, DOI-issuing archives, the artifact appendix, and the special challenges of storage artifacts that need specific devices, large traces, or long endurance runs on the separate post-acceptance timeline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-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.