Short
sickn33/agentic-awesome-skills
Rewrite the previous response more briefly while preserving the substance.
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
MITAuto-check passed
Install Fast Author Response
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-author-response --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/FAST-Skills/skills/fast-author-response .claude/skills/fast-author-response && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "fast-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-response into .claude/skills/fast-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-author-response", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-responseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-author-response --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/FAST-Skills/skills/fast-author-response .agents/skills/fast-author-response && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "fast-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-response into .agents/skills/fast-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-author-response", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-author-response --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/FAST-Skills/skills/fast-author-response .cursor/skills/fast-author-response && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "fast-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-response into .cursor/skills/fast-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-author-response", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path FAST-Skills/skills/fast-author-response--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-author-response --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/FAST-Skills/skills/fast-author-response .gemini/skills/fast-author-response && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "fast-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-response into .gemini/skills/fast-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-author-response", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-author-responseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/FAST-Skills/skills/fast-author-response .github/skills/fast-author-response && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "fast-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-response into .github/skills/fast-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-author-response", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-author-response --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/FAST-Skills/skills/fast-author-response .opencode/skills/fast-author-response && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "fast-author-response" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-author-response into .opencode/skills/fast-author-response/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-author-response", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
fast-author-response- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 599 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…
- Drafting USENIX FAST author responses
- SKILL.md covers Triage (both turns), Turn 1 — the author-response…, Turn 2 — the one-shot-revision… and Reviewer pushback patterns, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Resubmitted at the next deadline for a terminal accept/reject
What it does
Fast Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Drafting USENIX FAST author responses
- Resubmitted at the next deadline for a terminal accept/reject
Example prompts
- “/fast-author-response”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Fast Author Response loads about 1.5k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 599 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 599 words, ~1,470 tokens.
Download SKILL.mdSave it as
.claude/skills/fast-author-response/SKILL.md (or your agent's skills folder).- name
- fast-author-response
- description
- 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 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, written to fit the response form. One decision-critical point per reviewer beats an exhaustive reply. Concede what is true, correct what is misread, and point to exactly where the answer already lives in the submitted paper or artifact. Typical high-value moves for a storage paper:
- Point to the testbed table / firmware / preconditioning detail a reviewer thought was missing.
- Clarify that a number is a device-counter measurement, not an estimate, with the section reference.
- If asked for a baseline or a crash test you cannot run in the window, say what you can commit to and how you would bound the gap — do not paste unverifiable new results.
Turn 2 — the one-shot-revision change ledger (the distinctive FAST move)
A one-shot revision is a bounded, terminal revise-and-resubmit: the revised paper, submitted at the next deadline, can only be accepted or rejected. The response is a change ledger: for every required item, either do it and show it, or (rarely) explain precisely why it is infeasible and what you did instead.
[R1.1] Required: "Compare against the tuned stock compactor at steady state"
-> Action: DONE | added §5.3 + Table 4: bytes-written on <SSD, firmware> at steady state,
tuned baseline with equal budget; 2.1x reduction (95% CI ...)
-> Where: §5.3, Table 4; artifact/reproduce/rq2/
[R2.1] Required: "Show crash consistency is preserved"
-> Action: DONE | added §6: block-level record-and-replay at 500 injected crash points,
all recover a consistent state
-> Where: §6, artifact/crashtest/
[R2.2] Required: "Report tail latency, not mean"
-> Action: DONE | Fig. 7 now shows p50/p99/p99.9 under load
[R3.1] Requested: "Add a second datacenter trace"
-> Action: PARTIAL | added one archived production trace; a second is under NDA and cannot be
shared, so external validity is bounded explicitly in §7The rule that turns a one-shot revision into an acceptance: every required item is visibly done. Because the second read is terminal, a required change that is neither done nor squarely addressed is what causes the reject — there is no third round to fix it.
Show full SKILL.md (220 more words)Show less
Reviewer pushback patterns
| Pushback | What it signals | FAST-ready response |
|---|---|---|
| "Was the SSD preconditioned?" | Steady-state / device-state doubt | Show the preconditioning protocol and re-report at steady state |
| "You report mean, not tail, latency" | Latency-distribution objection | Add p99/p99.9 distributions under load |
| "Baseline isn't tuned / is old hardware" | Comparison-fairness doubt | Re-run tuned, same hardware and state; report new numbers |
| "You never crash-test the durability claim" | Consistency-verification gap | Add fault-injection / record-and-replay recovery results |
| "WA is estimated, not measured" | Measurement-soundness doubt | Read bytes-written from device counters; show the script |
| "Does this hold beyond one drive/datacenter?" | External-validity limit | Add devices/traces or bound the claim explicitly |
Anonymity in the response (easy to slip)
- Refer to your own prior work in the third person, as in the paper.
- Describe artifact/trace additions without linking an identity-revealing repository or host; use the anonymized location.
- Do not thank a named collaborator, funder, or hardware donor inside the response.
- Do not name your system, product, or datacenter even when a new result would read better with it.
Calibration
- Respond to the criterion the reviewer actually raised, not the one you would rather defend.
- Length and format norms for the response, and the exact one-shot-revision instructions, vary by cycle; follow the current instructions precisely.
- The revised paper — not the ledger — must carry the argument; the ledger is a map to the changes.
Output format
[Turn] author-response rebuttal / one-shot-revision change ledger
[Priority issue] <reviewer concern>
[Decision dimension] significance / measurement soundness / device state / baseline / consistency / clarity
[Change ledger] <required item -> DONE/PARTIAL/infeasible-with-reason + where in paper/artifact>
[Anonymity check] <no identity leak in the response: passed/issues>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in FAST-Skills/skills/fast-author-response of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fast Author Response next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Fast Author Response this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Shortsickn33/agentic-awesome-skills | 47k | 1 repos | ~281 | Automated safety check: Pass | MIT | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Hermes Agent Skill AuthoringNousResearch/hermes-agent | 252k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Icassp Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Aaai Author Responsebrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~924 | Automated safety check: Pass | MIT |
Similar skills
Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Hermes Agent Skill Authoring
NousResearch/hermes-agent
Author in-repo SKILL.md files: frontmatter and structure. An agent skill from NousResearch/hermes-agent.
Icassp Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an ICASSP rebuttal or author response to reviews, covering the recently added and short author-response window, the single-blind setting where reviewers already…
Aaai Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance…
Edbt Author Response
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when drafting EDBT author responses across the two turns of a cycle — the short author-feedback reply on the initial reviews, and the in-cycle revise-and-resubmit change…
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Fast Author Response
What does Fast Author Response do?
A skill your agent uses when drafting USENIX FAST author responses, covering the short pre-notification rebuttal during the author-response period and — distinctively — the one-shot-revision change…. Fast Author Response is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Fast Author Response?
Fast Author Response fits situations like: drafting USENIX FAST author responses; resubmitted at the next deadline for a terminal accept/reject.
How do I install Fast Author Response in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a claude-code`. Or copy the skill folder (FAST-Skills/skills/fast-author-response in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fast-author-response in your project. Claude Code loads it when a task matches its description.
How do I install Fast Author Response in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a codex`. Or copy the skill folder (FAST-Skills/skills/fast-author-response in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fast-author-response in your project. Codex loads it when a task matches its description.
Can I use Fast Author Response in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-author-response -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fast-author-response, .gemini/skills/fast-author-response, .github/skills/fast-author-response and .opencode/skills/fast-author-response in your project.
What does Fast Author Response need to run?
SKILL.md names no scripts, command-line tools or credentials: Fast Author Response is instructions for the agent only.
Does Fast Author Response access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Fast Author Response safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Fast Author Response use?
Fast Author Response is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Fast Author Response use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Fast Author Response?
Skills that share tags, products or a category with Fast Author Response: Short (sickn33/agentic-awesome-skills, 47k stars), Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Hermes Agent Skill Authoring (NousResearch/hermes-agent, 252k stars) and Icassp Author Response (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fast Author Response?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.