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.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response --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 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. - Correct factual misreadings first; a reviewer who misread a device table or a steady-state caveat is often persuadable. - Keep every word double-blind. Do not name your system's real name, institution, funder, datacenter, or a private trace URL, even to strengthen a point. ## Turn 1 — the author-response rebuttal Short and decision-focused, wr
- Triage (both turns)
- Turn 1 — the author-response rebuttal
- Turn 2 — the one-shot-revision change ledger (the distinctive FAST move)
- Reviewer pushback patterns
- Anonymity in the response (easy to slip)
- Calibration
- Output format
What does the fast-author-response skill do?
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.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response --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 984 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.