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 an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window…
MITAuto-check passed
Install Hpca Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-workflow .claude/skills/hpca-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 "hpca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-workflow into .claude/skills/hpca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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/HPCA-Skills/skills/hpca-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 hpca-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-workflow .agents/skills/hpca-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 "hpca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-workflow into .agents/skills/hpca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 hpca-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-workflow .cursor/skills/hpca-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 "hpca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-workflow into .cursor/skills/hpca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 HPCA-Skills/skills/hpca-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 hpca-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-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/HPCA-Skills/skills/hpca-workflow .gemini/skills/hpca-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 "hpca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-workflow into .gemini/skills/hpca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 hpca-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 hpca-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/HPCA-Skills/skills/hpca-workflow .github/skills/hpca-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 "hpca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-workflow into .github/skills/hpca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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 hpca-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 hpca-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/HPCA-Skills/skills/hpca-workflow .opencode/skills/hpca-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 "hpca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-workflow into .opencode/skills/hpca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-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
hpca-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 484 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window…
- Planning an HPCA project timeline from venue fit through the two-step July registration and paper gate
- SKILL.md covers The shape of the HPCA year, Milestones, Backward plan from the paper… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- The autumn review wait
What it does
Hpca Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.
Its SKILL.md is about 1.1k 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 an HPCA project timeline from venue fit through the two-step July registration and paper gate
- The autumn review wait
- The single rebuttal/revision window
- IEEE camera-ready
Example prompts
- “/hpca-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
Hpca Workflow loads about 1.1k tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 484 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). 484 words, ~1,062 tokens.
Download SKILL.mdSave it as
.claude/skills/hpca-workflow/SKILL.md (or your agent's skills folder).- name
- hpca-workflow
- description
- Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.
HPCA Workflow
Use this as the project-management skill for an HPCA submission. Replace every date with the current official timetable and plan backward from the late-July gate.
HPCA is a conference, not a journal: it has no standing editor-in-chief and no article-processing charge. It is run by the IEEE-CS Technical Committee on Computer Architecture (TCCA); the rotating leadership is the per-edition General and Program Chairs (HPCA 2027 program chairs were reported as Aamer Jaleel and Mattan Erez — 待核实), and the cost model is registration fees. Chairs rotate yearly, so re-check the current organization page rather than carrying a name forward.
The shape of the HPCA year
HPCA sits in the winter seat: a late-July deadline feeds an autumn review and a February/March conference. It is the last major architecture deadline of the summer, so a project that misses it waits for MICRO's spring gate or ISCA's November gate — plan the fallback before you need it.
Milestones
- Venue fit: confirm a measured microarchitectural cost meets a buildable mechanism whose behavior is the contribution.
- Evidence lock: freeze the mechanism, the simulator/silicon configuration, workloads, sampled regions, baselines, and the artifact mirror.
- Registration step: submit real title, abstract, authors, topics, and complete conflicts about a week before the paper.
- Paper step: upload the anonymous IEEE-template PDF and all HotCRP fields.
- Review wait: triage reviews for correctness, methodology, novelty, and reproducibility concerns as they land.
- Rebuttal/revision window: respond and revise in one combined window (recent cycles run a single window, not two rounds).
- Notification → acceptance: archive reviews, the response, and the submitted versions; then IEEE camera-ready, artifact evaluation on the AE HotCRP, and the winter talk.
Show full SKILL.md (213 more words)Show less
Backward plan from the paper deadline
| Weeks out (heuristic) | Hardware-evaluated milestone |
|---|---|
| 8+ | Mechanism implemented; fidelity contract (tool, config, workloads) fixed |
| 6 | Baseline sweeps complete; per-workload results, not just means |
| 4 | Real-silicon or validated-simulator numbers logged with machine state |
| 3 | Full draft in the IEEE two-column template |
| 2 | Internal mock review by an architecture-minded reader |
| 1 | Reference author-list check, anonymity sweep, artifact mirror assembled |
| 0 | Registration then paper on HotCRP |
These offsets are planning heuristics — anchor every one to the current official timetable, never to a previous cycle.
Failure modes by stage
- Infrastructure still churning at week 4 forces last-minute configuration changes no one has validated — the classic HPCA methodology reject in the making.
- Leaving template conversion to the final week surfaces overflow late; two-column architecture figures are tighter than a working draft's.
- Skipping the mock review forfeits the only chance to hear "your baseline is under-tuned" from a friend rather than a reviewer.
- Building the artifact mirror after the deadline under pressure is how anonymity leaks and un-pinned simulators ship.
Coordination notes
- Assign one named owner for the fidelity contract and another for the anonymity sweep; shared ownership is how both slip.
- Archive the exact submitted PDF, the artifact mirror, and the configuration files, since rebuttal replies must quote them precisely.
Output format
[Current stage] idea / evaluation / writing / registration / paper / window / accepted
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page/anonymity/instrument/reproducibility/artifact/presentation>
[Fallback venue] <MICRO / ISCA / ASPLOS branch if rejected>
[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 HPCA-Skills/skills/hpca-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Hpca 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 |
|---|---|---|---|---|---|---|
| Hpca Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | 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 | 4 repos | ~1.1k | Automated safety check: Pass | MIT | |
| VenueLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Table Fitasgeirtj/system_prompts_leaks | 69k | — | ~772 | Automated safety check: Pass | CC0-1.0 | |
| Furniture Fit Checkpascalorg/editor | 25k | — | ~5.1k | Automated safety check: Pass | MIT |
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.
Table Fit
asgeirtj/system_prompts_leaks
Keep a Markdown table readable in a narrow terminal of about 100 display columns - a wide table or one carrying prose in its cells wraps into unreadable ragged rows.
Furniture Fit Check
pascalorg/editor
Checks whether a sofa, table, bed or appliance fits in a measured Pascal room and reports only what the evidence supports, or asks for the missing measurements.
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…
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 Hpca Workflow
What does Hpca Workflow do?
A skill your agent uses when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window…. Hpca Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.
When should I use Hpca Workflow?
Hpca Workflow fits situations like: planning an HPCA project timeline from venue fit through the two-step July registration and paper gate; the autumn review wait; the single rebuttal/revision window; IEEE camera-ready.
How do I install Hpca Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-workflow -a claude-code`. Or copy the skill folder (HPCA-Skills/skills/hpca-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hpca-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Hpca Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-workflow -a codex`. Or copy the skill folder (HPCA-Skills/skills/hpca-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hpca-workflow in your project. Codex loads it when a task matches its description.
Can I use Hpca 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 hpca-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/hpca-workflow, .gemini/skills/hpca-workflow, .github/skills/hpca-workflow and .opencode/skills/hpca-workflow in your project.
What does Hpca Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Hpca Workflow is instructions for the agent only.
Does Hpca 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 Hpca 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 Hpca Workflow use?
Hpca 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 Hpca Workflow use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Hpca Workflow?
Skills that share tags, products or a category with Hpca 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 Table Fit (asgeirtj/system_prompts_leaks, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hpca Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.