icml-camera-ready — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited icml-camera-ready (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this after acceptance. ICML camera-ready work is unusually tied to public accountability because accepted papers publish the original submission, supplementary material, reviews, meta-reviews, rebuttal, and reviewer-author discussion along with camera-ready.
ICML 2026 camera-ready instructions require upload by May 28 AoE, allow a 9-page paper body, limit the camera-ready PDF to 20MB, require appendices in the PDF, provide no camera-ready supplementary material, ask for a lay summary, and require the format-checker code. They also introduce a financial conflict-of-interest disclosure rule for relevant cases.
presentation/registration questionnaire.
datasets, and repositories.
supplementary material.
What becomes visible on OpenReview for accepted ICML papers is broader than for many venues, so plan the deanonymization with that in mind.
| Item | Visibility after acceptance | Action |
|---|---|---|
| Original anonymous submission | Public | Ensure it still reads honestly next to the final paper |
| Reviews, meta-review, rebuttal, discussion | Public | Keep rebuttal claims consistent with camera-ready edits |
| Lay summary | Public-facing | Write for a non-specialist, avoid jargon |
| Financial conflict disclosure | Required where relevant | Confirm and complete for the current cycle |
The accepted optimizer paper moves all appendices into the single PDF, deanonymizes authors and funding, links the public code repository in the OpenReview code URL field, and writes a lay summary explaining "a faster training rule" without the convergence notation. The team runs the format checker and keeps the passing code, then double-checks that the rebuttal's promised in-regime plot actually appears, because both the rebuttal and the final paper are now public. Treat exact dates and page limits as annual; the 2026 baseline above should be re-verified against the current checklist.
[Camera-ready status] Ready / Needs fixes
[Public-record risks] <original submission/supplement/reviews/rebuttal visibility issue>
[Required uploads/forms] <PMLR/release/forms/format checker/lay summary>
[Artifact release] <repo/archive/code URL/data>
[Post-conference revision plan] <none or small corrections>~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.