Menu

Individual skill

fast-topic-selection

0upvotes

Use when deciding whether a storage project belongs at USENIX FAST or should be routed to OSDI, ATC, NSDI, EuroSys, HotStorage, MSST, SYSTOR, or a storage journal (ACM TOS), and when distinguishing FAST from general-systems siblings by storage-contribution shape, real-device evidence, and the two-deadline calendar.

FAST-Skills/skills/fast-topic-selection/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
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,400
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 Topic Selection

Decide the venue before drafting. FAST — the USENIX Conference on File and Storage Technologies — is
the **storage-specialized** flagship: its reviewers are file-system, SSD/NVM, key-value, caching,
and reliability people, and they read for a **storage contribution**, not a general systems result
that happens to touch disk. A technically strong paper whose real lesson is about scheduling,
networking, consensus, or an ML model is respected and then routed to OSDI, ATC, or NSDI.

## The routing question that matters most

The decisive question is rarely "is this systems work?" but **"is the core lesson a *storage*
lesson — about how data is laid out, written, cached, made durable, or kept consistent — that a
storage reviewer would recognize as theirs?"** If yes, FAST. If the storage angle is incidental to
a broader OS/distributed/networking result, a general-systems venue fits better.
Back to top