Individual skill

hpca-writing-style

Use when revising an HPCA paper for the mechanism-to-behavior first-page arc, a measured motivation before the fix, a checkable mechanism description, numbers that name their instrument, and 11-page compression that leaves slack for the single rebuttal/revision window.

HPCA-Skills/skills/hpca-writing-style/SKILL.md

Read pinned source

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.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# HPCA Writing Style

Use this to shape an HPCA paper's prose and structure. The house style rewards a
paper built around **one mechanism-to-behavior claim**, motivated by a measured cost
and evidenced on a named instrument. Reopen the current page limit before trusting
the compression advice below.

## The first-page arc

An HPCA first page should carry, in order: **the measured problem → why existing
mechanisms miss it → the mechanism → the behavior it produces → what the numbers rest
on**. A reviewer should finish the abstract and first column knowing what you built,
what it costs, and what it changes — before any implementation detail.
Back to top