fast-related-work
Use when positioning a USENIX FAST submission against the storage-systems literature across FAST, OSDI, ATC, SOSP, EuroSys, HotStorage, MSST, and the storage journals (ACM TOS), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-related-work --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 Related Work Use this to audit novelty and eligibility. FAST reviewers are close to the storage literature and expect to see where your paper sits relative to the nearest prior work — stated as a **delta**, not a list. Because many landmark storage systems appeared at OSDI, ATC, SOSP, or EuroSys rather than FAST, covering the right lanes matters. Reopen the current call for concurrent-submission, anonymity, and prior-publication rules before advising. ## Positioning checks - **Separate the storage novelty from the engineering effort.** What is new: a design that exploits a media property, a mechanism that removes a storage cost, a measurement method, a reliability finding, or an evidence regime nobody had covered on real devices? - **Cover the storage lanes.** FAST reviewers expect the storage venues *and* the storage-relevant systems venues, not just the papers nearest your method (see the table). A bibliography missing the obvious OSDI/ATC/SOSP predecessor reads as unaware. - **Write delta-first.** Each closely related system gets one sentence naming what it did and one naming what you do differently — often the delta is a storage quantity (it cut reads but paid write ampl
- Positioning checks
- Storage literature lanes
- Delta-first positioning vignette
- Concurrent and prior-version judgment calls
- Eligibility red flags
- Output format
What does the fast-related-work skill do?
Use when positioning a USENIX FAST submission against the storage-systems literature across FAST, OSDI, ATC, SOSP, EuroSys, HotStorage, MSST, and the storage journals (ACM TOS), writing delta-first contrast rather than a citation catalog, keeping self-citations double-blind, and handling concurrent, preprint, and prior-version overlap.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-related-work --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.