mlsys-camera-ready
Use when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository identity, reconciling promised rebuttal edits, the reserved-ticket registration window for authors, and sequencing camera-ready work against the artifact-evaluation deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.
# MLSys Camera Ready Use this after an MLSys acceptance. Two things make this venue's post-acceptance phase unusual: proceedings are published on the conference's own open archive (proceedings.mlsys.org, no publisher paywall and no APC), and the artifact-evaluation deadline lands in the same post-notification stretch — in 2026, notifications came January 25-26 and AE submissions were due March 8, so camera-ready and artifact packaging compete for the same weeks. Plan them as one project. ## Post-acceptance timeline (2026-cycle anchors) | Milestone | 2026 anchor | Owner risk | |---|---|---| | Notification | January 25-26, 2026 | — | | Camera-ready deadline | 待核实 — appears in the decision email, not verified on a public page | Missing it silently drops the paper's polish window | | Artifact submission to AE site | March 8, 2026 | Same people who owe the camera-ready | | AE review window | March 8 - April 8, 2026 | Authors answer AE questions anonymously | | Conference | May 18-22, 2026, Bellevue | Speaker travel, visas | The camera-ready page allowance for accepted papers could not be verified from public pages (待核实): take limits, forms, and the exact due date from the decision email
- Post-acceptance timeline (2026-cycle anchors)
- De-anonymization sweep (research track)
- Reconciling the review record
- Camera-ready package checklist
- Proceedings metadata and long-term findability
- Talk and poster preparation
- Registration and presentation logistics
- Output format
Confirm no anonymization debris survived the flip pdftotext camera_ready.pdf - | grep -inE 'anonym|blinded|redacted|under review' | head Confirm metadata now identifies the authors intentionally pdfinfo camera_ready.pdf | grep -iE 'author|title'
What does the mlsys-camera-ready skill do?
Use when preparing an accepted MLSys paper for publication on proceedings.mlsys.org, covering de-anonymization of the research-track PDF, restoring company and repository identity, reconciling promised rebuttal edits, the reserved-ticket registration window for authors, and sequencing camera-ready work against the artifact-evaluation deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill mlsys-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.