Individual skill

micro-writing-style

Use when drafting or revising a MICRO paper's prose and structure — building the characterization-motivated introduction, budgeting 11 appendix-free pages, drawing the mechanism walkthrough a microarchitect can re-implement, and pairing every speedup claim with its area, storage, and power cost line.

MICRO-Skills/skills/micro-writing-style/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
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,410
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
writing 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 · 6,702 bytes

Read excerpt


# MICRO Writing Style

A MICRO paper is an engineering argument: *this pattern exists in real workloads,
here is a piece of hardware that exploits it, here is what it costs, here is what it
pays*. The style rules below encode how the microarchitecture community reads.

## The four-beat argument

1. **Characterization beat.** Open with measured evidence that the exploitable
   behavior exists — a miss-pattern histogram, a stall-cycle breakdown, a
   reuse-distance CDF — from real workloads, before any mechanism appears. MICRO
   reviewers trust a paper that observed the machine before modifying it.
2. **Insight beat.** One sentence naming the property your hardware will exploit
   ("dead blocks announce themselves by burst-then-silence access"). If the insight