Agent skill

Hpca Experiments

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when auditing an HPCA evaluation: declaring the fidelity contract (simulator, configuration, workloads, sampled regions, validation), matching each claim to its instrument…

MITAuto-check passed

Install Hpca Experiments

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-experiments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ 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-experiments .claude/skills/hpca-experiments && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "hpca-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments into .claude/skills/hpca-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-experiments", 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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-experiments --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-experiments .agents/skills/hpca-experiments && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "hpca-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments into .agents/skills/hpca-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-experiments", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-experiments --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-experiments .cursor/skills/hpca-experiments && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "hpca-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments into .cursor/skills/hpca-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-experiments", 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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path HPCA-Skills/skills/hpca-experiments

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-experiments --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-experiments .gemini/skills/hpca-experiments && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "hpca-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments into .gemini/skills/hpca-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-experiments", 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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-experiments

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ 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-experiments .github/skills/hpca-experiments && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "hpca-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments into .github/skills/hpca-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-experiments", 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills hpca-experiments --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ 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-experiments .opencode/skills/hpca-experiments && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "hpca-experiments" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/HPCA-Skills/skills/hpca-experiments into .opencode/skills/hpca-experiments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hpca-experiments", 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-experiments
GitHub stars: 1.2k
Token cost: ~989 tokens
SKILL.md length: 390 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when auditing an HPCA evaluation: declaring the fidelity contract (simulator, configuration, workloads, sampled regions, validation), matching each claim to its instrument…

Auditing an HPCA evaluation: declaring the fidelity contract (simulator
SKILL.md covers Declare the fidelity contract, Match each claim to its…, Capture machine state for… and Tune baselines honestly, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Sampled regions

What it does

Hpca Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an HPCA evaluation: declaring the fidelity contract (simulator, configuration, workloads, sampled regions, validation), matching each claim to its instrument, capturing real-silicon machine state, tuning baselines honestly, and reporting per-workload distributions rather than a single mean.

Its SKILL.md is about 990 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

Auditing an HPCA evaluation: declaring the fidelity contract (simulator
Sampled regions
Matching each claim to its instrument
Capturing real-silicon machine state

Example prompts

“/hpca-experiments”

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 Experiments loads about 989 tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 390 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~82
When it runs · the whole SKILL.md, loaded when a task matches: ~989

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). 390 words, ~989 tokens.

Download SKILL.mdSave it as .claude/skills/hpca-experiments/SKILL.md (or your agent's skills folder).

name: hpca-experiments
description: Use when auditing an HPCA evaluation: declaring the fidelity contract (simulator, configuration, workloads, sampled regions, validation), matching each claim to its instrument, capturing real-silicon machine state, tuning baselines honestly, and reporting per-workload distributions rather than a single mean.

HPCA Experiments

Use this to stress-test an HPCA evaluation before the July gate. Architecture reviews are won and lost on methodology: a mechanism can be sound and still be rejected if the numbers cannot be trusted against their instrument.

Declare the fidelity contract

Every HPCA evaluation rests on a contract the paper must state explicitly:

Tool and version. Which simulator (and commit), or which real machine.
Fidelity scope. What the model captures and what it abstracts — an in-order functional model and a cycle-level OoO model make different claims believable.
Configuration. Core width, cache hierarchy, memory/DRAM timing model, interconnect — the parameters a reviewer needs to reproduce the setup.
Workloads and regions. The suite, the inputs, and how regions were sampled (e.g., SimPoint-style sampling) rather than run to completion.
Validation. What the timing models were validated against, with the error.

A number outside its contract is unreviewable; a contract stated up front pre-empts half the methodology objections.

Match each claim to its instrument

Claim type	Credible instrument	Not credible from
Cycle-level speedup	Validated cycle-level simulator	A functional/trace model with no timing
Energy/power	Modeled power tool with stated assumptions, or measured silicon	Hand-waved "should save energy"
Real-world behavior	Silicon with captured governor/turbo/SMT/NUMA state	A simulator alone, presented as measurement
Area/cost	Synthesis or a cited model	An unsupported "small overhead"

Do not let a claim borrow credibility from an instrument that cannot support it.

Show full SKILL.md (160 more words)Show less

Capture machine state for silicon

Every real-hardware number needs host provenance: frequency governor, turbo, SMT, NUMA policy, kernel and firmware versions, plus trial counts and dispersion. A single run on an unpinned machine is noise dressed as a result.

Tune baselines honestly

The most common HPCA methodology objection is an under-tuned baseline. Give prior mechanisms their best reasonable configuration, sweep the parameters that matter, and report where your mechanism is neutral or loses — a paper that only ever wins is less believable, not more.

Report the distribution

Report per-workload results, not only a geomean. Mark the workloads where the mechanism helps, is neutral, and hurts, and explain the losses. Sensitivity studies (cache size, core count, bandwidth) belong in the paper or appendix, because the first reviewer question is "does this hold off your chosen point?"

Pre-submission audit

text

1. Is the fidelity contract stated in full (tool, scope, config, workloads, validation)?
2. Does each headline claim name a credible instrument for its type?
3. Are silicon numbers accompanied by machine state, trials, and dispersion?
4. Are baselines tuned to their best config, with a sweep, not a single point?
5. Are results per-workload with neutral/loss cases marked and explained?
6. Do sensitivity studies show the result survives off the chosen operating point?

Output format

text

[Fidelity contract] complete / partial / missing
[Instrument match] claims matched / total claims
[Silicon provenance] state+trials+dispersion captured? (Y/N/NA)
[Baseline tuning] best-config + sweep? (Y/N)
[Distribution] per-workload with losses explained? (Y/N)
[Top methodology risks] <ordered>

Methodology expectations shift by cycle — reopen the current CFP and recent HPCA program norms before treating any convention here as fixed.

Files

Just SKILL.md in HPCA-Skills/skills/hpca-experiments of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Hpca Experiments 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.

Hpca Experiments compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Hpca Experiments this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~989	Automated safety check: Pass	MIT	11 days ago
Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep	17k	1 repos	~2.7k	Automated safety check: Notes	MIT	yesterday
Experiment Auditwanshuiyin/Auto-claude-code-research-in-sleep	17k	—	~3.2k	Automated safety check: Notes	MIT	yesterday
Auditing Experiments FlagsPostHog/posthog	40k	—	~956	Automated safety check: Pass	Custom licence	today
Arize Evaluatorgithub/awesome-copilot	40k	2 repos	~8.1k	Automated safety check: Notes	MIT	today
Production Auditaffaan-m/ECC	275k	1 repos	~1.9k	Automated safety check: Pass	MIT	3 days ago

Similar skills

Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
17k GitHub starsUsed in 1 repo~2.7k tokens
DatabasesAuto-check: notes
Experiment Audit
wanshuiyin/Auto-claude-code-research-in-sleep
Audit experiment integrity before claiming results. An agent skill from wanshuiyin/Auto-claude-code-research-in-sleep.
17k GitHub stars~3.2k tokensUpdated yesterday
DatabasesAuto-check: notes
Auditing Experiments Flags
PostHog/posthog
Official
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations.
40k GitHub stars~956 tokensUpdated today
Auto-check passed
Arize Evaluator
github/awesome-copilot
Official
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
40k GitHub starsUsed in 2 repos~8.1k tokens
AI & LLM EngineeringAuto-check: notes
Production Audit
affaan-m/ECC
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.
275k GitHub starsUsed in 1 repo~1.9k tokens
Product & Project ManagementAuto-check passed
LLM Evaluation
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
32k GitHub starsUsed in 13 repos~3.5k tokens
AI & LLM EngineeringAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 11 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 11 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 11 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 11 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 11 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 11 days ago
Auto-check passed

Questions about Hpca Experiments

What does Hpca Experiments do?

A skill your agent uses when auditing an HPCA evaluation: declaring the fidelity contract (simulator, configuration, workloads, sampled regions, validation), matching each claim to its instrument…. Hpca Experiments is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when auditing an HPCA evaluation: declaring the fidelity contract (simulator, configuration, workloads, sampled regions, validation), matching each claim to its instrument, capturing real-silicon machine state, tuning baselines honestly, and reporting per-workload distributions rather than a single mean.

When should I use Hpca Experiments?

Hpca Experiments fits situations like: auditing an HPCA evaluation: declaring the fidelity contract (simulator; sampled regions; matching each claim to its instrument; capturing real-silicon machine state.

How do I install Hpca Experiments in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a claude-code`. Or copy the skill folder (HPCA-Skills/skills/hpca-experiments in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/hpca-experiments in your project. Claude Code loads it when a task matches its description.

How do I install Hpca Experiments in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-experiments -a codex`. Or copy the skill folder (HPCA-Skills/skills/hpca-experiments in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/hpca-experiments in your project. Codex loads it when a task matches its description.

Can I use Hpca Experiments 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-experiments -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-experiments, .gemini/skills/hpca-experiments, .github/skills/hpca-experiments and .opencode/skills/hpca-experiments in your project.

What does Hpca Experiments need to run?

SKILL.md names no scripts, command-line tools or credentials: Hpca Experiments is instructions for the agent only.

Does Hpca Experiments 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 Experiments 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 Experiments use?

Hpca Experiments 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 Experiments use?

About 989 tokens (SKILL.md is roughly 4k 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 Experiments?

Skills that share tags, products or a category with Hpca Experiments: Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Experiment Audit (wanshuiyin/Auto-claude-code-research-in-sleep, 17k stars), Auditing Experiments Flags (PostHog/posthog, 40k stars) and Arize Evaluator (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hpca Experiments?

brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.

Install Hpca Experiments

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

HPCA Experiments

Declare the fidelity contract

Match each claim to its instrument

Capture machine state for silicon

Tune baselines honestly

Report the distribution

Pre-submission audit

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Hpca Experiments