Menu

Individual skill

fast-writing-style

0upvotes

Use when revising a USENIX FAST paper for a storage contribution on the first page, a design/mechanism narrative a storage reviewer can follow, an evaluation framed as the storage cost it changes (write amplification, tail latency, endurance, crash consistency), double-blind wording, and disciplined use of the USENIX two-column page budget.

FAST-Skills/skills/fast-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
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,410
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 Writing Style

Use this when revising the main paper. FAST papers are read by storage systems people, so they need
a **storage contribution stated on the first page** and an evaluation a storage reviewer trusts. The
failure this skill prevents is a technically fine paper that reads like a general systems demo or a
throughput-bar benchmark with "storage" in the title.

## Revision rules

- **Lead with the storage contribution:** the storage problem a practitioner recognizes, the
  *storage cost* current designs pay (write amplification, tail latency, endurance, space, or a
  consistency gap), your design or finding, real-device evidence, and what changes for storage
  systems.
- **Frame the evaluation as a cost you change, not a speed you win.** State up front which storage
Back to top