Individual skill
hpca-experiments
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-Skills/skills/hpca-experiments/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,405
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- legal Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,964 bytes
Read excerpt
# 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,