micro-submission
Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-submission --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 Submission Run this audit against the exact PDF headed to HotCRP. Anchors below are the MICRO 2026 (59th) cycle — CFP and submission guidelines at `microarch.org/micro59/submit/`, checked 2026-07-08. Every number is a snapshot; reopen the current cycle's pages. ## Three traps that are specifically MICRO's 1. **Deadlines run on US Eastern time.** MICRO 2026 closed abstracts on March 31 and papers on April 7, each at 11:59 PM **EDT**. Authors trained on AoE venues lose up to a working day by assuming AoE. Convert to every co-author's timezone in writing during deadline week. 2. **The abstract deadline is a registration gate, one week early.** No abstract in HotCRP by the first date means no paper submission at all. Register placeholders for every plausible paper; withdrawing is free, adding late is impossible. 3. **No appendix. At all.** The 2026 guidelines allow at most 11 pages of content plus unlimited references — and explicitly permit **no appendix**. Anything you planned to park after the references must be cut, absorbed into the 11 pages, or moved to an anonymized artifact repository (see `micro-supplementary`). ## Format gate table (2026 guidelines) | Rule | 2026 sett
- Three traps that are specifically MICRO's
- Format gate table (2026 guidelines)
- Anonymity, MICRO flavor
- Mechanical pre-flight
- HotCRP sequencing for deadline week
- What the abstract registration should actually contain
- Also decide: main track or Industry Track
- If something goes wrong at the wire
- Output format
page count and font floor
pdfinfo paper.pdf | grep Pages
pdffonts paper.pdf | awk 'NR>2 {print $1}' | sort -u # spot rasterized/tiny fonts manually
page numbers present? (render page 2 footer and look)
pdftotext -f 2 -l 2 paper.pdf - | tail -3
reference hygiene: no "et al." allowed inside entries
grep -n "et al" references.bib && echo "FIX: expand all author lists"
identity leakage
pdftotext paper.pdf - | grep -inE "(our (prior|previous) work|anonymous|acknowledg)"
exiftool paper.pdf | grep -iE "author|creator"What does the micro-submission skill do?
Use when auditing a MICRO submission before HotCRP upload — the 11-page-plus-references limit with no appendix allowed, EDT (not AoE) deadline arithmetic, the abstract-registration gate a week before the paper, minimum 9pt fonts, mandatory page numbers, all-author reference entries, and MICRO's visual-plus-automated format inspection.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-submission --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 984 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.