fast-writing-style
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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-writing-style --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 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 quantity the paper moves; a reader should know by the end of the intro whether the headline is bytes-written, p99 latency, drive lifetime, or recovery correctness. - **Pair every claim with proportional, real-device evidence** — named drives and firmware, standard workloads/traces, a distribution not just a mean, a device counter not an estimate — not adjectives. - **Make the device reality visible early.** A stora
- Revision rules
- Storage paper skeleton
- Sentence-level rewrites
- Storage-metric discipline
- Vignette: compressing a design-plus-study paper
- Output format
What does the fast-writing-style skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-writing-style --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.