Project Timeline Report
thedotmack/claude-mem
Writes a narrative Journey Into report on a project's whole development history, built from the timeline that claude-mem has recorded.
A skill your agent uses when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a…
MITAuto-check passed
Install Fast Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-workflow --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-workflow .claude/skills/fast-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-workflow into .claude/skills/fast-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-workflow", 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-workflowType 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-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-workflow --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-workflow .agents/skills/fast-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-workflow into .agents/skills/fast-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-workflow", 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-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-workflow --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-workflow .cursor/skills/fast-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-workflow into .cursor/skills/fast-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-workflow", 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-workflow--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-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills fast-workflow --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-workflow .gemini/skills/fast-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-workflow into .gemini/skills/fast-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-workflow", 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-workflowInstalls 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-workflow -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-workflow .github/skills/fast-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-workflow into .github/skills/fast-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-workflow", 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-workflow -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-workflow --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-workflow .opencode/skills/fast-workflow && 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-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/FAST-Skills/skills/fast-workflow into .opencode/skills/fast-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fast-workflow", 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-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 702 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a…
- Planning a USENIX FAST project timeline from venue fit through choosing a Spring
- SKILL.md covers Choose the deadline, then plan…, Milestones, Backward plan from the… and The two-deadline reality and…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Double-blind submission
What it does
Fast Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.
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
- Planning a USENIX FAST project timeline from venue fit through choosing a Spring
- Double-blind submission
- The author-response period
- A one-shot revision
Example prompts
- “/fast-workflow”
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 Workflow loads about 1.5k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 702 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). 702 words, ~1,475 tokens.
Download SKILL.mdSave it as
.claude/skills/fast-workflow/SKILL.md (or your agent's skills folder).- name
- fast-workflow
- description
- Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.
FAST Workflow
Use this as the project-management skill for a FAST submission. Replace every date with the current official timetable and work backwards from the deadline you choose. FAST — the USENIX Conference on File and Storage Technologies — runs two deadlines a year, has an author-response period, and can issue a one-shot revision that spans into the next deadline, so plan for a longer arc than a plain accept/reject conference.
FAST is a USENIX conference: it has no standing editor-in-chief and no article-processing charge. Rotating leadership is the per-edition Program Co-Chairs and the program committee, and the cost model is registration plus USENIX membership — proceedings are open access. Chairs and the Artifact Evaluation Committee rotate yearly; re-check the current committee page rather than carrying a name forward (FAST '27 rosters: 待核实 beyond what the CFP names).
Choose the deadline, then plan backward
FAST '27 offers Spring (submit 17 Mar 2026, notify 4 Jun 2026, final files 28 Jul 2026) and Fall (submit 15 Sep 2026, notify 8 Dec 2026, final files 26 Jan 2027). Pick by evidence readiness — storage measurements at steady state on real, aged devices take real calendar time — not by whichever is nearest. As of 2026-07-09 the Spring round is notified and the live target is the Fall deadline, 15 Sep 2026.
Milestones
- Venue fit: confirm FAST over OSDI/ATC/EuroSys and that the core lesson is storage
(
fast-topic-selection). - Evidence lock: freeze the testbed (devices, firmware, kernel), the workloads/traces, the device-state protocol (aging, fill, TRIM), the baselines, and the metrics.
- Registration: register real title, abstract, authors, topics, and conflicts on the correct Spring/Fall HotCRP instance.
- Submission: upload the anonymized, double-blind PDF and the availability statement.
- Author response: during the response window, answer reviewer questions with existing evidence or a concrete, feasible plan.
- Decision: Accept / Accept-with-shepherding / One-shot Revision / Reject.
- Shepherding or one-shot revision (if issued): make the required changes; a one-shot revision may demand new experiments and is resubmitted at the next deadline.
- Acceptance: prepare the open-access camera-ready, pursue USENIX artifact badges on the AEC's own timeline, register, and present.
Backward plan from the submission deadline
| Weeks out (heuristic) | Storage-evaluation milestone |
|---|---|
| 12+ | Testbed fixed: device models/firmware, kernel, mkfs options; workloads/traces chosen |
| 10 | Device-state protocol locked (aging/preconditioning, fill level, TRIM); baselines built and tuned |
| 8 | Measurement runs complete at steady state; device counters (SMART/logs) captured; provenance logged |
| 6 | Analysis done; tail-latency distributions, write-amplification, endurance projections computed |
| 4 | Full draft in the USENIX template; artifact + trace-replay scripts assembled and anonymized |
| 3 | Internal mock review by a storage reader |
| 2 | Caveats hardened, related-work delta sharpened, page limit met |
| 1 | Double-blind sweep on PDF and artifact; availability statement final |
| 0 | Register the abstract on the correct HotCRP, then upload |
These offsets are planning heuristics only — anchor every one to the current Important Dates block, never to a previous cycle's calendar. Note that storage runs (aging a drive, replaying a long trace, an endurance test) can dominate the schedule; size them explicitly.
Show full SKILL.md (216 more words)Show less
The two-deadline reality and one-shot revision
- Missing one deadline is not a lost year. The other FAST deadline is months away — but so is a sibling (OSDI/ATC/EuroSys) date; factor that into routing rather than idling.
- A one-shot revision is a second full deadline, not a formality. Its instructions can require specific new experiments, the revised paper is re-read, and it can be rejected. Budget the revision window like a fresh submission, and note the paper stays under review at FAST during it, so it cannot go elsewhere in parallel.
Failure modes by stage
- Testbed still moving at week 6 forces last-minute measurements nobody audited — the classic storage-soundness reject in the making.
- Reporting fresh-out-of-box instead of steady-state numbers invites the "did you precondition?" objection that can sink an SSD paper.
- Leaving the anonymized artifact and trace hosting to the final week is how a device dump, hostname, or personal trace URL leaks identity under double-blind.
- Treating a one-shot revision as an accept and under-budgeting its experiments turns a winnable revision into a reject.
Coordination notes
- Assign one owner for the testbed/provenance log and another for the double-blind sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, artifact, and (later) the response/revision documents — the revision round must quote reviews precisely and stay anonymous.
Output format
[Current stage] idea / evidence / writing / registration / submitted / response / shepherd-or-revision / accepted
[Target deadline] Spring / Fall <date and source, or unknown>
[Critical path] <three tasks that determine readiness — often measurement-time-bound>
[Risk register] <page limit / anonymity / device state / provenance / tail latency / artifact>
[Owner map] <task -> person or role>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Fast Workflow 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 Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Project Timeline Reportthedotmack/claude-mem | 99k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Timelinegreensock/gsap-skills | 16k | 3 repos | ~1.1k | Automated safety check: Pass | MIT | |
| VenueLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Building Incident Timeline With Timesketchmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.4k | Automated safety check: Notes | Apache-2.0 | |
| Generating Forensic Timelines With Hayabusamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GSAP Timeline
greensock/gsap-skills
Teaches the GSAP timeline API for sequencing animations: gsap.timeline(), the position parameter, labels, defaults, nesting and playback control.
Venue
LeoYeAI/openclaw-master-skills
Music venue where AI agents stream concerts as mathematics. An agent skill from LeoYeAI/openclaw-master-skills.
Building Incident Timeline With Timesketch
mukul975/Anthropic-Cybersecurity-Skills
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data (including Plaso output) for attack chain reconstruction and investigation…
Generating Forensic Timelines With Hayabusa
mukul975/Anthropic-Cybersecurity-Skills
Run Hayabusa against collected Windows EVTX files to apply Sigma detection rules and produce a prioritized, chronological CSV/JSON timeline with severity levels, MITRE ATT&CK mappings, and…
Performing Timeline Reconstruction With Plaso
mukul975/Anthropic-Cybersecurity-Skills
Builds comprehensive forensic super-timelines using Plaso (log2timeline and psort) to correlate events across file system metadata, event logs, browser history, and registry artifacts into a unified…
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 Workflow
What does Fast Workflow do?
A skill your agent uses when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a…. Fast Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a USENIX FAST project timeline from venue fit through choosing a Spring or Fall deadline, double-blind submission, the author-response period, shepherding or a one-shot revision, artifact evaluation, and the open-access camera-ready, with backward-planning offsets tuned to storage evaluation and honest handling of the two-deadline cycle.
When should I use Fast Workflow?
Fast Workflow fits situations like: planning a USENIX FAST project timeline from venue fit through choosing a Spring; double-blind submission; the author-response period; A one-shot revision.
How do I install Fast Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-workflow -a claude-code`. Or copy the skill folder (FAST-Skills/skills/fast-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/fast-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Fast Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill fast-workflow -a codex`. Or copy the skill folder (FAST-Skills/skills/fast-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/fast-workflow in your project. Codex loads it when a task matches its description.
Can I use Fast Workflow 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-workflow -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-workflow, .gemini/skills/fast-workflow, .github/skills/fast-workflow and .opencode/skills/fast-workflow in your project.
What does Fast Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Fast Workflow is instructions for the agent only.
Does Fast Workflow 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 Workflow 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 Workflow use?
Fast Workflow 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 Workflow 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 Workflow?
Skills that share tags, products or a category with Fast Workflow: Project Timeline Report (thedotmack/claude-mem, 99k stars), GSAP Timeline (greensock/gsap-skills, 16k stars), Venue (LeoYeAI/openclaw-master-skills, 2.2k stars) and Building Incident Timeline With Timesketch (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Fast Workflow?
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.