micro-related-work
Use when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's all-author citation format, and verifying venue attribution via dblp before citing.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-related-work --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MICRO Related Work At MICRO the related-work section is a *mechanism taxonomy*, not a bibliography tour. Reviewers — who probably wrote some of the cited papers — check three things: did you find the nearest mechanisms, do you know how yours differs structurally, and did you compare against the right one in the evaluation. ## The five lanes to sweep | Lane | Where it lives | What reviewers check | |---|---|---| | Direct ancestors of your mechanism | MICRO/ISCA/HPCA/ASPLOS, last ~5 years first, then classics | The named predecessor is in your evaluation, reimplemented (`micro-experiments`) | | Same problem, different layer | ASPLOS, OSDI/SOSP, PLDI (software attacks on your bottleneck) | You explain why hardware is still warranted | | Modeling & methodology you rely on | MICRO/ISCA tool papers (e.g., CACTI @ MICRO 2007, McPAT @ MICRO 2009), TACO/CAL journals | Versions cited match versions used | | Industry disclosures | Hot Chips talks, ISSCC papers, patents, vendor optimization manuals | A shipped equivalent of your idea would be fatal to novelty — find it before reviewers do | | Workload/characterization studies | IISWC, SIGMETRICS, arch venues | Your motivating characterizatio
- The five lanes to sweep
- Differentiate on structure and cost, not adjectives
- Venue attribution: verify before you cite
- Handling your own preprints and prior papers
- Format and anonymity constraints on the section
- Timing the sweep
- Building the section under MICRO's page economics
- Output format
dblp API: confirm venue + year + pages before the entry goes in the .bib curl -s "https://dblp.org/search/publ/api?q=utility-based+cache+partitioning&format=json" \
What does the micro-related-work skill do?
Use when building a MICRO paper's related-work coverage and positioning — sweeping the four-venue architecture literature plus journals and industry disclosures, differentiating by mechanism structure and cost rather than by numbers, obeying MICRO's all-author citation format, and verifying venue attribution via dblp before citing.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-related-work --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.