Individual skill

isca-writing-style

Use when drafting or revising an ISCA paper's prose — organizing 11 pages around one architectural insight, writing the motivation section from measured data, describing mechanisms at reviewer-checkable precision with figures that carry the design, and keeping quantitative claims calibrated to the instrument behind them.

ISCA-Skills/skills/isca-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

# ISCA Writing Style

An ISCA paper is an argument that a piece of machine organization should exist. The
prose conventions below are how the architecture community expects that argument to
be laid out — learned from the venue's canon and enforced, softly but consistently,
by its reviewers. Format facts (11 pages of single-spaced two-column text excluding
references, IEEE-flavored template for the 2026 edition) are the verified 2026
snapshot; recheck the current guidelines page before formatting.

## One insight, stated as a mechanism-behavior link

Before drafting, complete this sentence and pin it above the desk:

> Because <structural property of workloads or designs>, organizing the hardware as
Back to top