Individual skill

fast-author-response

Use when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change ledger that maps every required change (including any newly required storage experiments) to a concrete result, resubmitted at the next deadline for a terminal accept/reject.

FAST-Skills/skills/fast-author-response/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 Author Response

Use this after FAST reviews arrive. FAST has **two distinct speaking turns**, and conflating them is
a common mistake: a short **author-response (rebuttal)** during the pre-notification window, and — if
you receive a **one-shot revision** — a full **change ledger** accompanying a revised paper that is
re-read for a terminal accept/reject. Both keep double-blind: the response and any revision material
must not reveal authors, institutions, systems by name, or a private repository.

## Triage (both turns)

- Answer what affects the decision: the storage contribution's significance, soundness of the
  measurement, device/state credibility, baseline fairness, tail-latency and endurance evidence,
  crash-consistency, and clarity.
- Use evidence that already exists or that the revision will concretely add — never a vague promise.
Back to top