camera-ready

name	camera-ready
description	Coordinate camera-ready preparation for accepted research papers, including venue instructions, final PDF compliance, author metadata, appendix cleanup, artifact packaging, code/data release notes, license checks, and launch materials. Use when the user has an accepted or conditionally accepted paper and needs a rigorous pre-publication workflow.
version	0.1.0

Camera-Ready Paper Release

Use this skill when a paper is accepted and the user needs to transform the submission into a final proceedings-ready artifact.

Core stance

• Treat venue instructions as the source of truth. If instructions are missing, ask for the venue, year, track, and official camera-ready page.
• Preserve scientific claims. Do not introduce new results unless the user explicitly provides them.
• Separate final-paper tasks from public-release tasks.
• Keep an audit trail: every change should map to venue rule, reviewer request, artifact policy, or author preference.
• Flag legal, copyright, license, data-use, and human-subjects questions instead of resolving them confidently.

Intake

Collect or infer:

• venue, year, track, page limit, supplement limit, template version
• final title, authors, affiliations, acknowledgements, funding, conflicts
• accepted paper PDF/source, supplementary material, checklist, artifact files
• reviewer/shepherd requirements that must be reflected in final text
• public assets: code repo, data repo, project page, model weights, demo, video

Workflow

1. Build a camera-ready task board with required, optional, and risky sections.
2. Compare submission state against venue rules: page count, font/template, anonymization removal, author block, acknowledgements, ethics, references, appendix, checklist, and supplement naming.
3. Create a claim-freeze list. Identify claims, numbers, tables, and figures that should not change after acceptance without author approval.
4. Reconcile reviewer and shepherd requests with final text.
5. Audit all cross-references, citations, figure numbers, table numbers, appendix labels, URLs, DOIs, arXiv IDs, and repository links.
6. Prepare artifact release notes: environment, dependencies, quickstart, expected runtime, hardware, datasets, licenses, and reproducibility scope.
7. Draft public launch copy only after paper and artifact checks are stable.
8. Return a final go/no-go checklist with unresolved blockers.

Checks

PDF and source

• final template and class file match venue instructions
• no anonymous placeholders remain
• page count and supplement limits are respected
• author names, affiliations, emails, ORCID, and equal-contribution notes align
• acknowledgements include funding and compute credits where appropriate
• bibliography is complete, stable, and formatted by the venue style
• every figure and table is referenced in order
• accessibility basics: readable figures, high contrast, searchable text

Artifact and release

• README has install, quickstart, expected output, runtime, and troubleshooting
• license is explicit for code, data, model weights, and third-party assets
• secrets, tokens, private paths, internal URLs, and unreleased data are removed
• scripts run from a clean checkout or clearly state required credentials
• claims in the paper match what the artifact can actually reproduce

Public communication

• announcement avoids unsupported novelty or inflated impact
• social posts link to paper, code, data, project page, and demo where available
• acknowledgements and collaborator credit are accurate
• limitations and responsible-use notes are included when relevant

Output format

Return:

1. Camera-ready board: grouped by required, optional, and risky.
2. Compliance audit: venue rules checked, evidence, status.
3. Artifact release audit: files, licenses, reproducibility scope.
4. Final blockers: only issues that must be resolved before submission.
5. Launch copy: short announcement variants if requested.