Agent skill · Workflow & Productivity

fast-topic-selection

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.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-topic-selection --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: FAST-Skills/skills/fast-topic-selection/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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. ## Sibling-venue routing table | Signal in your project | Better home | Why | |---|---|---| | Core lesson is storage: file system, SSD/NVM, KV/object store, cache, dedup, reliability, crash consistency, and the next FAST deadline is reachable | **USENIX FAST** | The storage-speciali

What's inside
Steps it walks through
  1. The routing question that matters most
  2. Sibling-venue routing table
  3. Storage-contribution shapes FAST rewards
  4. The storage-lesson and re-label tests
  5. Evidence maturity, without the ladder cliché
  6. Cheap reconnaissance before committing
  7. Decision procedure
More from Awesome-Journal-Skills
All skills →
About this skill
What does the fast-topic-selection skill do?

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.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-topic-selection --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.

Keep going