micro-camera-ready
Use when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional post-AE artifact appendix, and IEEE/ACM publication logistics.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-camera-ready --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 Camera-Ready For the 2026 cycle: notification July 7, camera-ready **September 11, 2026** — nine weeks, with artifact evaluation (see `micro-artifact-evaluation`) running inside the same span and the symposium following in Athens, Oct 31 – Nov 4. This skill turns the acceptance email into a correct published record. ## The nine-week plan | Weeks | Work | |---|---| | 1 | Re-read reviews cold; extract every fix promised in the rebuttal into a tracked worklist | | 2–4 | Execute the worklist: new runs promised, clarified methodology text, corrected figures | | 3–6 | Artifact evaluation submission and evaluator support (parallel track) | | 7 | De-anonymization pass + acknowledgments + final reference audit | | 8 | Publisher formatting, copyright/rights forms, metadata | | 9 | Buffer; upload early — September 11 is also the AE endgame in recent cycles | ## De-anonymization is an additive diff, not a rewrite Produce the camera-ready as a reviewed diff against the accepted PDF: - Author block, affiliations, ORCIDs in. - **Acknowledgments restored** — people, funding agencies, grant numbers were *required to be absent* at submission (2026 guidelines), so they are easy to forget perm
- The nine-week plan
- De-anonymization is an additive diff, not a rewrite
- Page arithmetic changes
- Publication and indexing facts worth knowing
- Presentation pipeline (the deadline after the deadline)
- Post-camera-ready checklist
- Metadata that outlives the conference
- Output format
guardrails on the final build latexdiff accepted.tex camera.tex > diff.tex && pdflatex diff.tex # human-review the delta grep -n "et al" references.bib && echo "STILL banned at camera-ready: expand authors" grep -inE "anonym|under review|blind" camera.tex # stale scaffolding pdftotext camera.pdf - | grep -iE "acknowledg" || echo "MISSING acknowledgments?"
What does the micro-camera-ready skill do?
Use when a MICRO paper is accepted and the camera-ready is due — the nine-week July-to-September window in the 2026 cycle, de-anonymization and acknowledgments restoration, keeping the all-author reference rule, integrating rebuttal promises, the optional post-AE artifact appendix, and IEEE/ACM publication logistics.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-camera-ready --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.