fast-supplementary
Use when deciding what belongs in a USENIX FAST paper body versus its artifact and appendices, covering the USENIX two-column page budget (references excluded), the rule that decision-critical storage evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a storage paper between body and package.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-supplementary --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 Supplementary Use this when assembling FAST supplementary material. The governing rule is simple and strict: **the paper must be judgeable from the reviewed pages alone.** The artifact, traces, and any appendix support the paper; they do not hold the argument. Reviewers open the artifact at their discretion, so anything the decision depends on lives in the body. ## What goes where | Content | Body (within page budget) | Artifact / appendix | |---|---|---| | The storage claim and its headline result | Yes | — | | Core design or study protocol | Yes | Full parameter sweeps, extra configs | | The testbed: device models, firmware, state | Yes (summary table) | The complete machine/firmware inventory | | Headline storage metrics + the invariant test | Yes (WA/tail latency/crash test) | Full distributions, per-run logs | | Crash-consistency evidence for a durability claim | The result + method | The fault-injection / replay harness | | Workloads and traces | Named + why chosen | The trace archive and replay scripts | | Raw device counters, logs, scripts | — | Yes | | Reproduction instructions | A pointer | The README and run scripts | If a reviewer would need to open the artifact
- What goes where
- The page-budget discipline
- Double-blind supplementary rules
- Appendix and artifact-appendix architecture
- Vignette: splitting a file-system design paper
- Output format
What does the fast-supplementary skill do?
Use when deciding what belongs in a USENIX FAST paper body versus its artifact and appendices, covering the USENIX two-column page budget (references excluded), the rule that decision-critical storage evidence stays inside the reviewed pages, double-blind supplementary material, and how to split a storage paper between body and package.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-supplementary --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.