fast-submission
Use when auditing a USENIX FAST submission for HotCRP readiness, covering the choice between the Spring and Fall deadlines, abstract registration, the USENIX two-column template and 12-page (long) / 6-page (short) limit excluding references, double-blind anonymization, the artifact-availability story, and desk-reject triage before the AoE cutoff.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-submission --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 Submission Run this audit before uploading to the FAST HotCRP site. FAST — the USENIX Conference on File and Storage Technologies — publishes **open access via USENIX**, reviews **double-blind**, and runs **two deadlines a year**. The first decision you make is not about the PDF but about *which deadline* you are aiming at. Every number below was read from the FAST '26/'27 calls on 2026-07-09 via search renderings of the `usenix.org` URLs (see `resources/official-source-map.md`); treat them as a one-cycle snapshot and reopen the live call first. ## Pick the deadline first FAST '27 runs a **Spring** deadline (17 Mar 2026) and a **Fall** deadline (15 Sep 2026), each with its own HotCRP instance, author-response window, and notification date. Consequences: - Choose by readiness, not habit: a study that will be steady-state-solid in August targets **Fall**; do not rush it into a Spring slot it will fail. - Register at the **right** HotCRP site — the Spring and Fall instances are different URLs; an abstract registered on the wrong one does not carry over. - As of 2026-07-09 the live actionable target is the **FAST '27 Fall deadline, 15 Sep 2026**. ## Register the abstract early F
- Pick the deadline first
- Register the abstract early
- Format and page limit
- Double-blind sweep
- Availability story at submission time
- Desk-risk triage
- Final-week order of operations
- Reverify each cycle
- Output format
Mechanical pass on the submission PDF and any anonymized artifact archive pdfinfo paper.pdf | grep -Ei 'author|creator|producer' pdftotext paper.pdf - | grep -nEi 'github\.com/[a-z0-9-]+|zenodo\.org/record|our (system|lab|group)|acknowledg|grant' | head unzip -l artifact.zip | grep -Ei '\.git/|\.DS_Store|/home/|/Users/|hostname' | head grep -rni 'university\|@[a-z0-9.]*\.edu\|internal cluster\|<companyname>' artifact/ --include='*.md' | head
What does the fast-submission skill do?
Use when auditing a USENIX FAST submission for HotCRP readiness, covering the choice between the Spring and Fall deadlines, abstract registration, the USENIX two-column template and 12-page (long) / 6-page (short) limit excluding references, double-blind anonymization, the artifact-availability story, and desk-reject triage before the AoE cutoff.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-submission --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.