Menu

Individual skill

micro-topic-selection

0upvotes

Use when deciding whether a project belongs at MICRO (IEEE/ACM International Symposium on Microarchitecture) or should route to ISCA, HPCA, ASPLOS, DAC/ICCAD, SC, or MLSys — testing whether the mechanism truly lives inside the machine, gauging the MICRO evidence bar, and weighing the main track against the new Industry Track.

MICRO-Skills/skills/micro-topic-selection/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
No
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.

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

# MICRO Topic Selection

Decide venue before writing a single evaluation section. MICRO is the flagship
symposium *of the microarchitecture community specifically* — the 2026 edition is the
59th, which places its lineage back to the 1968 microprogramming workshops. Reviewers
here are calibrated to mechanisms measured in cycles, bytes of state, and milliwatts.

## The mechanism-residency test

Ask where the proposed mechanism physically lives and what evidence proves it works:

1. **State the mechanism in one sentence without naming any software component.** If
   you cannot — if the sentence needs "the compiler", "the OS", or "the runtime" as a
   load-bearing actor — the work is cross-stack and ASPLOS deserves a look first.
Back to top